4 sec in total
156 ms
3.4 sec
410 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 156 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
metastats.net performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value9.6 s
0/100
25%
Value27.8 s
0/100
10%
Value37,100 ms
0/100
30%
Value0.365
29/100
15%
Value60.4 s
0/100
10%
156 ms
67 ms
71 ms
245 ms
71 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 34% of them (50 requests) were addressed to the original Metastats.net, 17% (25 requests) were made to Art.hearthstonejson.com and 9% (13 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (787 ms) relates to the external source Art.hearthstonejson.com.
Page size can be reduced by 288.4 kB (6%)
4.7 MB
4.4 MB
In fact, the total size of Metastats.net main page is 4.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. 85% 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 4.3 MB which makes up the majority of the site volume.
Potential reduce by 61.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 13.5 kB, which is 19% 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 61.5 kB or 87% of the original size.
Potential reduce by 192.3 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 33.6 kB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 33.6 kB or 14% of the original size.
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 53 (47%)
113
60
The browser has sent 113 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 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
metastats.net
156 ms
clipboard.min.js
67 ms
c3.min.css
71 ms
bootstrap.min.css
245 ms
theme.css
71 ms
metastats.css
113 ms
animate.css
113 ms
font-awesome.min.css
109 ms
default.css
127 ms
adsbygoogle.js
132 ms
jquery-1.9.1.min.js
126 ms
jquery-ui.min.js
241 ms
bootstrap.min.js
127 ms
css
212 ms
zrt_lookup.html
284 ms
show_ads_impl.js
564 ms
favicon.png
203 ms
BAR_309.png
532 ms
demon%20hunter.png
202 ms
druid.png
203 ms
hunter.png
202 ms
mage.png
202 ms
paladin.png
203 ms
priest.png
330 ms
rogue.png
329 ms
shaman.png
328 ms
warlock.png
329 ms
warrior.png
329 ms
demonhunter.png
329 ms
BAR_309.png
339 ms
AV_330.png
348 ms
CORE_EX1_193.png
348 ms
SW_441.png
349 ms
REV_249.png
349 ms
REV_246.png
349 ms
CS3_028.png
349 ms
CORE_LOE_077.png
348 ms
REV_290.png
348 ms
REV_253.png
348 ms
REV_022.png
349 ms
REV_018.png
349 ms
REV_011.png
349 ms
BAR_065.png
348 ms
ONY_026.png
348 ms
AV_331.png
348 ms
TSC_052.png
348 ms
CORE_EX1_197.png
348 ms
REV_238.png
347 ms
BAR_735.png
348 ms
REV_252.png
348 ms
CORE_CFM_605.png
348 ms
TSC_216.png
348 ms
CORE_DRG_090.png
348 ms
AV_330.png
681 ms
CORE_EX1_193.png
682 ms
SW_441.png
683 ms
REV_249.png
693 ms
REV_246.png
743 ms
CS3_028.png
674 ms
CORE_LOE_077.png
719 ms
REV_290.png
675 ms
REV_253.png
726 ms
REV_022.png
692 ms
REV_018.png
697 ms
REV_011.png
693 ms
BAR_065.png
719 ms
ONY_026.png
743 ms
AV_331.png
708 ms
TSC_052.png
722 ms
CORE_EX1_197.png
727 ms
REV_238.png
740 ms
BAR_735.png
757 ms
REV_252.png
764 ms
CORE_CFM_605.png
741 ms
TSC_216.png
762 ms
CORE_DRG_090.png
787 ms
TSC_209.png
750 ms
analytics.js
416 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
407 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
396 ms
TSC_209.png
152 ms
gem_common.png
227 ms
gem_epic.png
226 ms
gem_rare.png
225 ms
gem_legendary.png
225 ms
fontawesome-webfont.woff
110 ms
collect
175 ms
cookie.js
91 ms
integrator.js
87 ms
ads
483 ms
ads
570 ms
reactive_library.js
105 ms
1604312994502737569
87 ms
abg_lite.js
120 ms
window_focus.js
138 ms
qs_click_protection.js
138 ms
rx_lidar.js
169 ms
one_click_handler_one_afma.js
147 ms
icon.png
36 ms
integrator.js
76 ms
ads
357 ms
ads
581 ms
zrt_lookup.html
51 ms
gen_204
68 ms
pixel
69 ms
ad
272 ms
css2
62 ms
load_preloaded_resource.js
54 ms
042791247ab671b2831aa311d6583330.js
290 ms
interstitial_ad_frame.js
46 ms
feedback_grey600_24dp.png
396 ms
settings_grey600_24dp.png
494 ms
s
41 ms
activeview
78 ms
css
170 ms
3072851149515852947
497 ms
abg_lite.js
65 ms
omrhp.js
63 ms
UFYwWwmt.js
60 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
218 ms
KFOmCnqEu92Fr1Me5Q.ttf
225 ms
YrdBSjzfIHcYhYLmavhSyO_EhBrLUWpx5ykdL7H9Kqg.js
194 ms
Enqz_20U.html
98 ms
pixel
291 ms
ad
290 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
167 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
303 ms
gen_204
283 ms
bounce
258 ms
skeleton.js
381 ms
4169511451717987020
169 ms
cookie_push_onload.html
152 ms
pixel
126 ms
rum
124 ms
dpixel
424 ms
trk
436 ms
activeview
150 ms
rum
211 ms
activeview
64 ms
pixel
80 ms
pixel
78 ms
pixel
82 ms
sodar
75 ms
pixel
62 ms
pixel
46 ms
sodar2.js
31 ms
metastats.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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
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: