2 sec in total
390 ms
1.4 sec
216 ms
Welcome to deckstats.net homepage info - get ready to check Deckstats best content for United States right away, or after learning these important things about deckstats.net
Build and analyze your MTG deck. See deck price, mana curve, type distribution, color distribution, mana sources, card probabilities, proxies, ...
Visit deckstats.netWe analyzed Deckstats.net page load time and found that the first response time was 390 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
deckstats.net performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.9 s
30/100
25%
Value5.2 s
61/100
10%
Value380 ms
70/100
30%
Value0.079
95/100
15%
Value6.6 s
57/100
10%
390 ms
7 ms
9 ms
24 ms
18 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 34% of them (40 requests) were addressed to the original Deckstats.net, 9% (10 requests) were made to Us-u.openx.net and 9% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (449 ms) relates to the external source Securepubads.g.doubleclick.net.
Page size can be reduced by 273.1 kB (30%)
923.8 kB
650.7 kB
In fact, the total size of Deckstats.net main page is 923.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 560.5 kB which makes up the majority of the site volume.
Potential reduce by 28.0 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.0 kB or 75% of the original size.
Potential reduce by 32.7 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. Deckstats images are well optimized though.
Potential reduce by 155.7 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 155.7 kB or 61% of the original size.
Potential reduce by 56.7 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. Deckstats.net needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 78% of the original size.
Number of requests can be reduced by 79 (72%)
109
30
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Deckstats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
deckstats.net
390 ms
jquery-ui-1.9.2.custom.css
7 ms
jquery.jqplot.min.css
9 ms
jquery.tagsinput.css
24 ms
jquery.dataTables_themeroller.css
18 ms
global.1456690518.css
5 ms
statistik.1456703068.css
12 ms
merged.deck.1456702077.js
57 ms
t.js
15 ms
ga.js
84 ms
gpt.js
71 ms
loading_bar.gif
262 ms
widgets.js
102 ms
header_deckstats.png
67 ms
header_right_bg.png
62 ms
apple-touch-icon.png
64 ms
ui-icons_1f3a59_256x240.png
59 ms
eventbar_toggle.png
60 ms
23.png
61 ms
8.png
63 ms
0.png
63 ms
3.png
66 ms
7.png
64 ms
12.png
66 ms
11.png
67 ms
17.png
66 ms
5.png
66 ms
1.png
72 ms
4.png
67 ms
18.png
68 ms
15.png
68 ms
9.png
69 ms
16.png
69 ms
10.png
69 ms
ui-bg_flat_75_d6dbe0_40x100.png
69 ms
build.png
71 ms
stats.png
71 ms
manage.png
74 ms
proxies.png
73 ms
buy.png
71 ms
registration.png
71 ms
usgb.png
257 ms
de.png
255 ms
es.png
254 ms
ptbr.png
256 ms
it.png
253 ms
fr.png
356 ms
ui-bg_glass_75_d6dbe0_1x400.png
23 ms
ui-icons_445a88_256x240.png
23 ms
pubads_impl_81.js
38 ms
__utm.gif
61 ms
print.1428941246.css
58 ms
ads
449 ms
container.html
28 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
137 ms
likebox.php
204 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
48 ms
BdmCbeqDF1M.css
163 ms
34E4j2xurGO.css
201 ms
_rx8naC75Dy.js
275 ms
b94UUzHjapV.js
379 ms
0wM5s1Khldu.js
308 ms
TTCre3391I0.js
306 ms
jot
91 ms
jstag
21 ms
osd.js
7 ms
1
40 ms
acj
34 ms
pd
11 ms
1
21 ms
acj
30 ms
rr
11 ms
ri
9 ms
828be8e8-0a91-d2d0-1b69-18133fe704c6
45 ms
openx
7 ms
pixel
19 ms
getuid
21 ms
openx
4 ms
sd
6 ms
sd
9 ms
pd
10 ms
getjs.aspx
29 ms
rr
17 ms
ri
16 ms
OpenX.ashx
89 ms
cfcm.ashx
12 ms
sd
14 ms
sd
8 ms
sd
7 ms
getjs.static.js
64 ms
sd
51 ms
577359_429077347155056_1080896219_n.png
180 ms
wL6VQj7Ab77.png
37 ms
s7jcwEQH7Sx.png
44 ms
GetAd.aspx
16 ms
sd
3 ms
showad.js
7 ms
sd
25 ms
showad.js
20 ms
AdServerServlet
100 ms
400066.gif
18 ms
PugMaster
18 ms
p-P7x87XHnVfbWr.gif
14 ms
generic
13 ms
gr
14 ms
demconf.jpg
14 ms
Pug
39 ms
Pug
39 ms
Pug
35 ms
Pug
37 ms
amzn_ads.js
11 ms
I6-MnjEovm5.js
38 ms
f6T91Deal_q.js
80 ms
getad
27 ms
getjs.aspx
15 ms
GetAd.aspx
15 ms
deckstats.net accessibility score
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
deckstats.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
deckstats.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
EN
N/A
ISO-8859-15
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Deckstats.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Deckstats.net main page’s claimed encoding is iso-8859-15. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
deckstats.net
Open Graph data is detected on the main page of Deckstats. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: