Tools & Wizards About Us
tokyomtg.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

tokyomtg.com

[MTG Specialty Shop / TokyoMTG] Magic Cards & MTG Original Art online store

Page Load Speed

3.8 sec in total

First Response

26 ms

Resources Loaded

1.4 sec

Page Rendered

2.4 sec

tokyomtg.com screenshot

About Website

Click here to check amazing TokyoMTG content for United States. Otherwise, check out these important facts you probably never knew about tokyomtg.com

Worldwide Magic: The Gathering Specialty Store! We have all manner of cards and art (original and prints) available for purchase. At TokyoMTG, our professional team of buyers will buy and sell high-en...

Visit tokyomtg.com

Key Findings

We analyzed Tokyomtg.com page load time and found that the first response time was 26 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tokyomtg.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value53.8 s

0/100

25%

SI (Speed Index)

Value38.8 s

0/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.398

25/100

15%

TTI (Time to Interactive)

Value49.2 s

0/100

10%

Network Requests Diagram

tokyomtg.com

26 ms

tokyomtg.com

649 ms

js

88 ms

jquery-ui.min.css

64 ms

urv2rzb.css

114 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 47% of them (41 requests) were addressed to the original Tokyomtg.com, 45% (39 requests) were made to Media.wizards.com and 3% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (695 ms) relates to the external source Media.wizards.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.2 kB (3%)

Content Size

16.4 MB

After Optimization

15.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyomtg.com main page is 16.4 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. Only a small number of websites need less resources to load. Images take 15.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 148.2 kB

  • Original 162.4 kB
  • After minification 150.9 kB
  • After compression 14.2 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 148.2 kB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 192.3 kB

  • Original 15.1 MB
  • After minification 14.9 MB

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. TokyoMTG images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 131.7 kB

  • Original 962.7 kB
  • After minification 962.7 kB
  • After compression 831.1 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 131.7 kB or 14% of the original size.

CSS Optimization

-48%

Potential reduce by 69.0 kB

  • Original 142.6 kB
  • After minification 142.0 kB
  • After compression 73.6 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. Tokyomtg.com needs all CSS files to be minified and compressed as it can save up to 69.0 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

79

After Optimization

55

  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TokyoMTG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tokyomtg.com

tokyomtg.com

26 ms

tokyomtg.com

tokyomtg.com

649 ms

js

js

88 ms

jquery-ui.min.css

jquery-ui.min.css

64 ms

urv2rzb.css

urv2rzb.css

114 ms

keyrune.min.css

keyrune.min.css

58 ms

mana.css

mana.css

61 ms

bootstrap.min.css

bootstrap.min.css

66 ms

slick.css

slick.css

56 ms

slick-theme.css

slick-theme.css

59 ms

nouislider.min.css

nouislider.min.css

78 ms

fontawesome.min.css

fontawesome.min.css

103 ms

brands.min.css

brands.min.css

79 ms

regular.min.css

regular.min.css

77 ms

solid.min.css

solid.min.css

80 ms

style.css

style.css

72 ms

product-wrapper.css

product-wrapper.css

80 ms

contact-form.css

contact-form.css

81 ms

webbuying.css

webbuying.css

98 ms

logoWhiteSM.png

logoWhiteSM.png

96 ms

jp_40681d4c7b.png

jp_40681d4c7b.png

421 ms

jp_c5ea735e7e.png

jp_c5ea735e7e.png

416 ms

jp_93301367a5.png

jp_93301367a5.png

415 ms

jp_4757a3351b.png

jp_4757a3351b.png

341 ms

jp_7432225913.png

jp_7432225913.png

417 ms

jp_725f5e9cfa.png

jp_725f5e9cfa.png

481 ms

jp_9d47066af2.png

jp_9d47066af2.png

421 ms

jp_cc64f8c5b2.png

jp_cc64f8c5b2.png

478 ms

en_fdd807bcb6.png

en_fdd807bcb6.png

418 ms

en_fa47581585.png

en_fa47581585.png

419 ms

jp_707c4cf6cb.png

jp_707c4cf6cb.png

483 ms

jp_e34d947d46.png

jp_e34d947d46.png

544 ms

jp_2bb61540ab.png

jp_2bb61540ab.png

546 ms

jp_15657a3a4f.png

jp_15657a3a4f.png

478 ms

jp_736ba7d5dc.png

jp_736ba7d5dc.png

547 ms

banner_2024-08-07_mitsuhiroarita.jpg

banner_2024-08-07_mitsuhiroarita.jpg

92 ms

banner_2024-08-05_artistevent.jpg

banner_2024-08-05_artistevent.jpg

91 ms

banner_2024-08-02_blb.jpg

banner_2024-08-02_blb.jpg

98 ms

banner_2024-07-13_deckset.jpg

banner_2024-07-13_deckset.jpg

98 ms

banner_2024-06-14_mh3.jpg

banner_2024-06-14_mh3.jpg

96 ms

banner_2024-06-20_commander.jpg

banner_2024-06-20_commander.jpg

98 ms

banner_2024-07-05_acr.jpg

banner_2024-07-05_acr.jpg

99 ms

banner_2024-04-19_otj.jpg

banner_2024-04-19_otj.jpg

125 ms

banner_2023-07-22_tokyomtgsleeves.jpg

banner_2023-07-22_tokyomtgsleeves.jpg

100 ms

latest_2024-02-15_setlist.jpg

latest_2024-02-15_setlist.jpg

118 ms

latest_2024-02-15_eventcalendar.jpg

latest_2024-02-15_eventcalendar.jpg

124 ms

latest_2024-02-15_artprints.jpg

latest_2024-02-15_artprints.jpg

117 ms

9df37469-6e2d-4783-aad3-c897ecbc967d.jpg

9df37469-6e2d-4783-aad3-c897ecbc967d.jpg

55 ms

en_c5498d9dc0.png

en_c5498d9dc0.png

465 ms

jp_aca7d36020.png

jp_aca7d36020.png

467 ms

jp_9b97ae4942.png

jp_9b97ae4942.png

674 ms

jp_e8d978585d.png

jp_e8d978585d.png

471 ms

en_336197c4b3.png

en_336197c4b3.png

472 ms

jp_7QFRzyCOLM.png

jp_7QFRzyCOLM.png

691 ms

jp_7acd069ba7.png

jp_7acd069ba7.png

531 ms

jp_9936c3b2a2.png

jp_9936c3b2a2.png

534 ms

jp_ff0003e158.png

jp_ff0003e158.png

532 ms

jp_ef5ae527f9.png

jp_ef5ae527f9.png

594 ms

jp_5VJNhTWgqv.png

jp_5VJNhTWgqv.png

538 ms

jp_yTEiTVLVtY.png

jp_yTEiTVLVtY.png

566 ms

jp_3ba479102e.png

jp_3ba479102e.png

557 ms

en_abe38fe3a3.png

en_abe38fe3a3.png

540 ms

en_Wj56BO5dPz.png

en_Wj56BO5dPz.png

553 ms

en_2e2c89b572.png

en_2e2c89b572.png

561 ms

en_429578cbaf.png

en_429578cbaf.png

637 ms

en_iskmjq2jd9.png

en_iskmjq2jd9.png

606 ms

en_6595210f75.png

en_6595210f75.png

573 ms

en_5db38326f0.png

en_5db38326f0.png

594 ms

jquery.min.js

jquery.min.js

102 ms

jquery-ui.min.js

jquery-ui.min.js

115 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

126 ms

slick.min.js

slick.min.js

127 ms

nouislider.min.js

nouislider.min.js

124 ms

base.js

base.js

125 ms

main.js

main.js

124 ms

jp_7a39270594.png

jp_7a39270594.png

695 ms

cards.js

cards.js

314 ms

9df37469-6e2d-4783-aad3-c897ecbc967d.jpg

9df37469-6e2d-4783-aad3-c897ecbc967d.jpg

266 ms

p.css

p.css

57 ms

d

d

101 ms

d

d

102 ms

en_e058ba6a2c.png

en_e058ba6a2c.png

223 ms

en_a1136eaa48.png

en_a1136eaa48.png

276 ms

en_fd2bd95a3d.png

en_fd2bd95a3d.png

242 ms

fa-solid-900.ttf

fa-solid-900.ttf

61 ms

fa-regular-400.ttf

fa-regular-400.ttf

58 ms

fa-brands-400.ttf

fa-brands-400.ttf

59 ms

Accessibility Review

tokyomtg.com accessibility score

67

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

tokyomtg.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tokyomtg.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyomtg.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 Tokyomtg.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.

Social Sharing Optimization

tokyomtg.com

Open Graph description is not detected on the main page of TokyoMTG. 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: