4.3 sec in total
320 ms
2.6 sec
1.3 sec
Click here to check amazing Mtgen content for Ireland. Otherwise, check out these important facts you probably never knew about mtgen.net
Magic: The Gathering Sealed/Booster Generator: Generate accurate random Magic: The Gathering boosters and other such madness.
Visit mtgen.netWe analyzed Mtgen.net page load time and found that the first response time was 320 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mtgen.net performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value3.8 s
56/100
25%
Value1.6 s
100/100
10%
Value50 ms
100/100
30%
Value0.159
73/100
15%
Value2.5 s
98/100
10%
320 ms
25 ms
35 ms
151 ms
155 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 93% of them (109 requests) were addressed to the original Mtgen.net, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mtgen.net.
Page size can be reduced by 466.2 kB (5%)
9.5 MB
9.0 MB
In fact, the total size of Mtgen.net main page is 9.5 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. 55% of websites need less resources to load. Images take 9.4 MB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 12.3 kB, which is 17% 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 63.9 kB or 91% of the original size.
Potential reduce by 366.4 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. Mtgen images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Potential reduce by 3.9 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. Mtgen.net needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 73% of the original size.
Number of requests can be reduced by 3 (3%)
112
109
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mtgen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for CSS and as a result speed up the page load time.
mtgen.net
320 ms
css
25 ms
css
35 ms
html5reset.css
151 ms
home.css
155 ms
analytics.js
31 ms
home-bg.jpg
314 ms
logo-mtg.png
296 ms
logo-word.png
308 ms
logo-word.png
311 ms
logo-word.png
425 ms
logo-word.png
598 ms
logo-word.png
519 ms
logo-word.png
393 ms
logo-word.png
543 ms
logo-word.png
475 ms
logo-word.png
544 ms
logo-word.png
512 ms
logo-word.png
563 ms
logo-word.png
688 ms
logo-word.png
603 ms
logo-word.png
627 ms
logo-word.png
700 ms
logo-word.png
646 ms
logo-word.png
685 ms
logo-word.png
682 ms
logo-word.png
712 ms
logo-word.png
734 ms
logo-word.png
764 ms
logo-word.png
773 ms
logo-word.png
858 ms
logo-word.png
848 ms
logo-word.png
797 ms
logo-word.png
821 ms
logo-word.png
845 ms
logo-word.png
858 ms
logo-word.png
956 ms
logo-word.png
909 ms
logo-word.png
928 ms
logo-word.png
982 ms
logo-word.png
1036 ms
logo-word.png
1003 ms
collect
25 ms
W81bfaWiUicLSPbJhW-AToJ9FRurQkHWDDTe2Dq6d_c.ttf
9 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
22 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
24 ms
collect
75 ms
logo-word.png
718 ms
logo-word.png
779 ms
logo-word.png
884 ms
logo-word.png
772 ms
logo-word.png
795 ms
logo-word.png
691 ms
logo-word.png
661 ms
logo-word.png
663 ms
logo-word.png
722 ms
logo-word.png
670 ms
logo-word.png
751 ms
logo-word.png
705 ms
logo-word.png
685 ms
logo-word.png
690 ms
logo-word.png
679 ms
logo-word.png
673 ms
logo-word.png
681 ms
logo-word.png
694 ms
logo-word.png
766 ms
logo-word.png
768 ms
logo-word.png
692 ms
logo-word.png
695 ms
logo-word.png
695 ms
logo-word.png
701 ms
logo-word.png
697 ms
logo-word.png
688 ms
logo-word.png
701 ms
logo-word.png
701 ms
logo-word.png
703 ms
logo-word.png
706 ms
logo-word.png
680 ms
logo-word.png
664 ms
logo-word.png
675 ms
logo-word.png
764 ms
logo-word.png
647 ms
logo-word.png
638 ms
logo-word.png
641 ms
logo-word.png
595 ms
logo-word.png
642 ms
logo-word.png
617 ms
logo-word.png
617 ms
logo-word.png
582 ms
logo-word.png
583 ms
logo-word.png
628 ms
logo-word.png
611 ms
logo-word.png
593 ms
logo-word.png
577 ms
logo-word.png
561 ms
logo-word.png
560 ms
logo-word.png
613 ms
logo-word.png
652 ms
logo-word.png
600 ms
logo-word.png
561 ms
logo-word.png
557 ms
logo-word.png
533 ms
logo-word.png
563 ms
logo-word.png
549 ms
logo-word.png
557 ms
logo-word.png
559 ms
logo-word.png
552 ms
logo-word.png
546 ms
logo-word.png
563 ms
logo-word.png
533 ms
logo-word.png
545 ms
logo-word.png
603 ms
logo-word.png
542 ms
logo-word.png
536 ms
logo-word.png
560 ms
logo-word.png
529 ms
logo-word.png
527 ms
mtgen.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.
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.
mtgen.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mtgen.net SEO score
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 Mtgen.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 Mtgen.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.
mtgen.net
Open Graph description is not detected on the main page of Mtgen. 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: