19 sec in total
258 ms
17.7 sec
1 sec
Visit wizardtower.com now to see the best up-to-date Wizard Tower content for Canada and also check out these interesting facts you probably never knew about wizardtower.com
Help Solve the Murders! Preorder Today REGISTER FOR EVENTSSHOP SEALED PRODUCTS Pre-order Sealed ProductsRegister For Events https://youtu.be/b9uGTQdSZWE
Visit wizardtower.comWe analyzed Wizardtower.com page load time and found that the first response time was 258 ms and then it took 18.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
wizardtower.com performance score
name
value
score
weighting
Value20.4 s
0/100
10%
Value23.0 s
0/100
25%
Value28.3 s
0/100
10%
Value2,270 ms
6/100
30%
Value0.01
100/100
15%
Value39.5 s
0/100
10%
258 ms
2170 ms
307 ms
359 ms
369 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 58% of them (90 requests) were addressed to the original Wizardtower.com, 17% (26 requests) were made to Fonts.gstatic.com and 8% (12 requests) were made to Mtgcanada.com. The less responsive or slowest element that took the longest time to load (10.4 sec) belongs to the original domain Wizardtower.com.
Page size can be reduced by 3.4 MB (38%)
8.9 MB
5.6 MB
In fact, the total size of Wizardtower.com main page is 8.9 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. 75% 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 187.9 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 187.9 kB or 86% of the original size.
Potential reduce by 154.2 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. Wizard Tower images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 71% of the original size.
Potential reduce by 1.9 MB
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. Wizardtower.com needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 89% of the original size.
Number of requests can be reduced by 75 (60%)
126
51
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wizard Tower. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
wizardtower.com
258 ms
www.wizardtower.com
2170 ms
wp-emoji-release.min.js
307 ms
css
359 ms
css
369 ms
css
415 ms
css
476 ms
cache.skin.css
569 ms
settings.css
335 ms
css
154 ms
css
228 ms
css
297 ms
settings.css
314 ms
icomoon.css
385 ms
custom.style.css
776 ms
mobile.css
489 ms
default.min.css
486 ms
styles.min.css
591 ms
js_composer.min.css
2876 ms
print.css
675 ms
frontend.min.css
1836 ms
last_minute_fixes.css
947 ms
ultimate.min.css
1714 ms
Defaults.css
960 ms
jquery.js
1275 ms
jquery-migrate.min.js
1159 ms
lightbox.js
1471 ms
jquery.themepunch.tools.min.js
1815 ms
jquery.themepunch.essential.min.js
4872 ms
jquery.themepunch.revolution.min.js
2127 ms
theme.js
2134 ms
bootstrap.min.js
2144 ms
bootstrap-select.js
2690 ms
core.min.js
2334 ms
widget.min.js
2338 ms
accordion.min.js
2347 ms
mouse.min.js
2994 ms
slider.min.js
2524 ms
resizable.min.js
2606 ms
draggable.min.js
2774 ms
button.min.js
3355 ms
position.min.js
3041 ms
dialog.min.js
3084 ms
tabs.min.js
4767 ms
jquery-ui.css
152 ms
css
129 ms
css
145 ms
sortable.min.js
3069 ms
droppable.min.js
3196 ms
datepicker.min.js
3302 ms
menu.min.js
3357 ms
lightbox.js
559 ms
jquery.themepunch.tools.min.js
773 ms
jquery.themepunch.essential.min.js
1079 ms
font-awesome.css
3476 ms
autocomplete.min.js
3365 ms
css
66 ms
frontend.min.js
4260 ms
ultimate.min.js
4373 ms
modal-all.min.js
3837 ms
comment-reply.min.js
3354 ms
frontend.js
3336 ms
script.min.js
3501 ms
wp-embed.min.js
3468 ms
js_composer_front.min.js
3480 ms
fbevents.js
303 ms
Jori.png
2808 ms
DDOSE3.png
2639 ms
Brutal461.png
2803 ms
Advocate461.png
2801 ms
DDOSE2.png
2800 ms
Mar24-1.jpg
2057 ms
nayasha461.png
3936 ms
DDOSE.png
3934 ms
thopt461.png
4197 ms
Noisy-Light.png
391 ms
search.png
286 ms
twitch.png
291 ms
facebook.png
290 ms
twitter.png
287 ms
youtube.png
290 ms
rss.png
489 ms
wt-logo-1.png
497 ms
wt-logo-black.jpg
496 ms
mtg-logo.jpg
532 ms
kanatacg-logo.jpg
2044 ms
logo.png
531 ms
ORI_Key_Art.jpg
6886 ms
MTGSOI_EN-copy2.png
2026 ms
SOI_PW_Arlinn_Kord_image_gallery-1.jpg
2397 ms
c4rd4r7_MkPi3K9BtS.jpg
2864 ms
Chandra-Flamecaller_OGW_2560x1600_Wallpaper.jpg
10418 ms
398500000_Art.jpg
4669 ms
layer52.png
2598 ms
layer41.png
3189 ms
layer31.png
2796 ms
layer61.png
3071 ms
layer12.png
3216 ms
payments.png
3299 ms
subbutton4.png
3455 ms
390 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
1504 ms
BTu4SsVveqk58cdYjlaM9g.ttf
1506 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
1873 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
1503 ms
lato-reg.woff
2958 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
2082 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
2081 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
1505 ms
lato-bol.woff
3080 ms
zpv3sOKAbMf4wff105oLjw.ttf
2079 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
2078 ms
4cKlrioa77J2iqTqBgkRWg.ttf
2077 ms
lato-lig.woff
3377 ms
LgcV55siz7BRNdbO3Huj5g.ttf
1954 ms
analytics.js
1422 ms
loader0.js
1415 ms
cardlist.txt
2875 ms
revolution.extension.slideanims.min.js
2585 ms
revolution.extension.actions.min.js
2595 ms
revolution.extension.layeranimation.min.js
2743 ms
revolution.extension.navigation.min.js
2815 ms
revolution.extension.parallax.min.js
2875 ms
cross.png
2742 ms
loader.gif
2740 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
185 ms
fontawesome-webfont.woff
2988 ms
8649-136-10-3678.js
148 ms
collect
119 ms
c
204 ms
application2.js
356 ms
storage.html
635 ms
ui-bg_flat_75_ffffff_40x100.png
484 ms
coloredbg.png
608 ms
revicons.woff
607 ms
storage.js
520 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
24 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
22 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
20 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
264 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
265 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
263 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
261 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
261 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
259 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
262 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
260 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
258 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
259 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
258 ms
visits
389 ms
jquery.js
95 ms
defa91a2fa32bf2f40ae871208354401.css
119 ms
buttons-dark.png
38 ms
wizardtower.com 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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wizardtower.com 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
Page has valid source maps
wizardtower.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wizardtower.com 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 Wizardtower.com 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.
wizardtower.com
Open Graph description is not detected on the main page of Wizard Tower. 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: