695 ms in total
45 ms
490 ms
160 ms
Visit metastats.net now to see the best up-to-date Meta Stats content for United States and also check out these interesting facts you probably never knew about metastats.net
Real-Time Hearthstone Stats and Meta Reports Generated using actual hearthstone games. Game data is collected using our plugins for Hearthstone Deck Tracker and TrackoBot. All stats are calculated usi...
Visit metastats.netWe analyzed Metastats.net page load time and found that the first response time was 45 ms and then it took 650 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
metastats.net performance score
name
value
score
weighting
Value1.8 s
88/100
10%
Value5.0 s
27/100
25%
Value5.6 s
52/100
10%
Value3,310 ms
2/100
30%
Value0.368
29/100
15%
Value15.0 s
7/100
10%
45 ms
197 ms
13 ms
26 ms
44 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 64% of them (52 requests) were addressed to the original Metastats.net, 23% (19 requests) were made to Art.hearthstonejson.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (224 ms) relates to the external source Art.hearthstonejson.com.
Page size can be reduced by 337.2 kB (9%)
3.7 MB
3.3 MB
In fact, the total size of Metastats.net main page is 3.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 50.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 14.4 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.5 kB or 87% of the original size.
Potential reduce by 285.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Meta Stats images are well optimized though.
Potential reduce by 93 B
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.
Potential reduce by 1.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Metastats.net has all CSS files already compressed.
Number of requests can be reduced by 13 (21%)
63
50
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meta Stats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
metastats.net
45 ms
js
197 ms
clipboard.min.js
13 ms
c3.min.css
26 ms
bootstrap.min.css
44 ms
theme.css
19 ms
metastats.css
24 ms
animate.css
17 ms
font-awesome.min.css
25 ms
default.css
27 ms
adsbygoogle.js
196 ms
jquery-1.9.1.min.js
27 ms
jquery-ui.min.js
32 ms
bootstrap.min.js
27 ms
css
38 ms
favicon.png
134 ms
TOY_330.png
191 ms
deathknight.png
75 ms
demon%20hunter.png
75 ms
druid.png
75 ms
hunter.png
75 ms
mage.png
75 ms
paladin.png
74 ms
priest.png
82 ms
rogue.png
82 ms
shaman.png
82 ms
warlock.png
88 ms
warrior.png
88 ms
demonhunter.png
88 ms
gem_legendary.png
95 ms
TOY_330.png
114 ms
gem_common.png
94 ms
YOG_511.png
96 ms
gem_epic.png
94 ms
CORE_CFM_790.png
112 ms
VAC_514.png
113 ms
gem_rare.png
96 ms
CORE_RLK_066.png
114 ms
VAC_323.png
114 ms
DEEP_017.png
112 ms
TOY_826.png
115 ms
CORE_RLK_051.png
124 ms
VAC_329.png
115 ms
VAC_437.png
123 ms
RLK_024.png
124 ms
CORE_RLK_035.png
124 ms
VAC_305.png
128 ms
VAC_301.png
128 ms
VAC_702.png
128 ms
CORE_RLK_741.png
128 ms
TTN_737.png
128 ms
YOG_516.png
129 ms
YOG_511.png
141 ms
CORE_CFM_790.png
153 ms
VAC_514.png
125 ms
CORE_RLK_066.png
143 ms
VAC_323.png
143 ms
DEEP_017.png
145 ms
TOY_826.png
157 ms
CORE_RLK_051.png
157 ms
VAC_329.png
172 ms
VAC_437.png
165 ms
RLK_024.png
168 ms
CORE_RLK_035.png
181 ms
VAC_305.png
222 ms
VAC_301.png
223 ms
VAC_702.png
222 ms
CORE_RLK_741.png
224 ms
TTN_737.png
223 ms
YOG_516.png
224 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf
112 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf
122 ms
fontawesome-webfont.woff
92 ms
show_ads_impl.js
127 ms
14 ms
31 ms
27 ms
22 ms
19 ms
20 ms
18 ms
metastats.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
metastats.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
metastats.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metastats.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Metastats.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
metastats.net
Open Graph description is not detected on the main page of Meta Stats. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: