vrm.dev Vrm.dev

   
VR向け3Dアバターファイルフォーマット | VRM

Domain Summary

What percent of global Internet users visit Vrm.dev?

• 3.83E-5% of global Internet users visit Vrm.dev

How many people visit Vrm.dev each day?

• Vrm.dev receives approximately 1.9K visitors and 3,396 page impressions per day.

Which countries does Vrm.dev receive most of its visitors from?

• Vrm.dev is mostly visited by people located in Japan,United States,Russian Federation.

How much Vrm.dev can earn?

• Vrm.dev should earn about $8.18/day from advertising revenue.

What is Vrm.dev estimated value?

• Estimated value of Vrm.dev is $7,682.81.

What IP addresses does Vrm.dev resolve to?

• Vrm.dev resolves to the IP addresses 185.199.109.153.

Where are Vrm.dev servers located in?

• Vrm.dev has servers located in San Francisco, California, 94107, United States.

vrm.dev Profile

Title:VR向け3Dアバターファイルフォーマット | VRM Description:VRMドキュメントサイト
Category:Games / Video Games Consoles and Accessories
Edit Site Info

What technologies does vrm.dev use?

These are the technologies used at vrm.dev. vrm.dev has a total of 8 technologies installed in 8 different categories.
Documentation
Docusaurus Docusaurus
Static Site Generator
Docusaurus Docusaurus
CDN
Fastly Fastly
PaaS
GitHub Pages GitHub Pages
Security
HSTS HSTS
Miscellaneous
Open Graph Open Graph
webpack webpack
Caching
Varnish Varnish
JavaScript Frameworks
React React

vrm.dev Traffic Analysis

This website is viewed by an estimated 1.9K visitors daily, generating a total of 3.4K pageviews. This equates to about 57.1K monthly visitors. Vrm.dev traffic has increased by 9.48% compared to last month.
Daily Visitors1.9K
7.66%
Monthly Visits57.1K
9.48%
Pages per Visit1.80
30.73%
Visit duration00:40
26.36%
Bounce Rate48.85%
30.54%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,886
Monthly Visits:
57,146
Pages per Visit:
1.80
Daily Pageviews:
3,396
Avg. visit duration:
00:40
Bounce rate:
48.85%
Global Reach:
3.83E-5%
Monthly Visits (SEMrush):
16,147
Monthly Unique Visitors (SEMrush):
13,978
Monthly Visits (SimilarWeb):
57,738
HypeRank:
n/a
SEMrush Rank:
1,718,580
SimilarWeb Rank:
569,626
*All traffic values are estimates only.

Traffic sources

Direct:
17.22%
Referral:
17.03%
Search:
50.17%
Social:
15.58%
Paid:
0%

Desktop vs Mobile

Desktop:
78.04%
Mobile:
21.96%

Total Visits Last 3 Months

65K
FEB
52.2K
MAR
57.1K
APR

Visitors by country

Country
Users%
 
Japan 38.37%
 
United States 12.21%
 
Russian Federation 4.11%
 
Germany 3.80%
 
Brazil 3.03%

Which sites are competitors to vrm.dev?

Websites similar to vrm.dev are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Last update was 29 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with vrm.dev in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
473

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  vrm.dev
Rank:
(Rank based on keywords, cost and organic traffic)
  1,718,580
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  210
Organic Traffic:
(Number of visitors coming from top 20 search results)
  453
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $263.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $8.2 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $245.4 and annual gross revenue of approximately $3K. Based on these figures, the site's net worth is estimated at around $7.7K.

How much would vrm.dev make?

Daily Revenue:
$8.18
Monthly Revenue:
$245.40
Yearly Revenue:
$2,985.70
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 415$2.00
 
Japan 1,303$0.47
 
Germany 129$0.18
 
Brazil 103$0.14
 
Russian Federation 140$0.06

Loss of money due to Adblock?

Daily Revenue Loss:
$0.44
Monthly Revenue Loss:
$13.16
Yearly Revenue Loss:
$160.08
Daily Pageviews Blocked:
166
Monthly Pageviews Blocked:
4,971
Yearly Pageviews Blocked:
60,480

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 75$0.36
 
Germany 37$0.05
 
Japan 39$0.01
 
Brazil 6$0.01
 
Russian Federation 8$0.00

How much is vrm.dev worth?

Website Value:
$7.7K

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
vrm.dev
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
vrm.dev
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
vrm.dev
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is vrm.dev hosted? ▼

Vrm.dev may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
185.199.109.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
San Francisco
California, CA
94107
United States, US
 

Other sites hosted on 185.199.109.153

How fast does vrm.dev load? ▼

The average loading time of vrm.dev is 49 ms. The Desktop speed index is 96 and mobile speed index is 93.
Average Load Time:
49 ms

Page Speed (Google PageSpeed Insights) - Desktop

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)421ms 92% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 92% 7% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 7% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)687ms 97% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 97% 1% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 1% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)91ms 94% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 94% 5% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 5% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)687ms 99% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 99% 0% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)432ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 5% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 5% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)738ms 97% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 97% 1% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 1% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)73ms 95% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 95% 3% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 3% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)853ms 98% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 98% 0% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
3rd parties  
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint 0.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Time to Interactive 0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact

Page Speed (Google PageSpeed Insights) - Mobile

93
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)633ms 92% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 84% 10% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 10% 4% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)909ms 97% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)0 94% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)909ms 99% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 95% 1% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 1% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)542ms 89% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 89% 8% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 8% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)966ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)165ms 81% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 81% 15% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 15% 3% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 3%
Largest Contentful Paint (LCP)1.1s 97% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 97% 1% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 1% 1% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 1%

Lab Data

3rd parties  
3rd party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of 3rd party code
Largest Contentful Paint 2.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Speed Index 4.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Time to Interactive 2.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading

Does vrm.dev use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on vrm.dev are reduced by 71%.
vrm.dev use gzip compression.
Original size: 14.95 KB
Compressed size: 4.31 KB
File reduced by: 10.64 KB (71%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  SAFE

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. vrm.dev supports HTTPS.
 vrm.dev supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: vrm.dev
Organization:
Location:
Issuer: R10
Valid from: Apr 24 11:57:38 2025 GMT
Valid until: Jul 23 11:57:37 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 vrm.dev supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Thu, 15 May 2025 08:27:26 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"6825a56e-3bca"
expires: Fri, 23 May 2025 08:33:01 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: E4F9:3C2689:5978A3:613E90:68303061
accept-ranges: bytes
age: 0
date: Fri, 23 May 2025 08:23:01 GMT
via: 1.1 varnish
x-served-by: cache-chi-klot8100056-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1747988581.273079,VS0,VE32
vary: Accept-Encoding
x-fastly-request-id: b9715639267e7d59d213ffd7cf88035a415a1a58
content-length: 4409

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
SOA 21600
Mname ns-cloud-b1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 4
Refresh 21600
Retry 3600
Expire 259200
Minimum TTL 300
A 185.199.110.153 14340
A 185.199.111.153 14340
A 185.199.108.153 14340
A 185.199.109.153 14340
NS ns-cloud-b3.googledomains.com 10740
NS ns-cloud-b1.googledomains.com 10740
NS ns-cloud-b2.googledomains.com 10740
NS ns-cloud-b4.googledomains.com 10740