3.4 sec in total
156 ms
2.5 sec
755 ms
Visit dailymtg.com now to see the best up-to-date Daily MTG content and also check out these interesting facts you probably never knew about dailymtg.com
The official source for Magic: The Gathering news, announcements, podcast, guest writers, and articles. Directly from the people who develop MTG.
Visit dailymtg.comWe analyzed Dailymtg.com page load time and found that the first response time was 156 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dailymtg.com performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value21.5 s
0/100
25%
Value17.7 s
0/100
10%
Value3,830 ms
1/100
30%
Value0.133
81/100
15%
Value19.9 s
2/100
10%
156 ms
141 ms
142 ms
145 ms
149 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Dailymtg.com, 13% (10 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Cdn.datatables.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Magic.wizards.com.
Page size can be reduced by 1.9 MB (22%)
8.9 MB
6.9 MB
In fact, the total size of Dailymtg.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 6.4 MB which makes up the majority of the site volume.
Potential reduce by 56.6 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 7.7 kB, which is 11% 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 56.6 kB or 79% of the original size.
Potential reduce by 13.0 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. Daily MTG images are well optimized though.
Potential reduce by 1.3 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.3 MB or 77% of the original size.
Potential reduce by 525.4 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. Dailymtg.com needs all CSS files to be minified and compressed as it can save up to 525.4 kB or 87% of the original size.
Number of requests can be reduced by 21 (33%)
63
42
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Daily MTG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
articles
156 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
141 ms
css_y9XbJmW0x68vNj1BvLRwO-MN-0DIVvVlJHKpVT0DIUc.css
142 ms
css_lSKXYZIAeUSlMB-hlkYpJ_qukJOzfOUpWJ3BZL5O_Lo.css
145 ms
css_U8wSEPTdxSSpxNba2T1lkZFE5GlY-4rlW7H0H-b1VMw.css
149 ms
css_hK3xMdPfntEhetaTcQmRTd5pDhumxquVke2x6aVmbso.css
335 ms
css
24 ms
jquery.dataTables.css
10 ms
dataTables.responsive.css
13 ms
js_Bua3V7s16xhn2yjwAWIH8Q0UCvf3SgluOlYdKTEQLZ0.js
265 ms
js_gCXw6L5rIDJME29Rlz4GAxqmES__wEcM6Hej53BvUKM.js
277 ms
js_87n_9LAk5PGZe23QkefuJr9njqZfCqCAvNGZRRy2u4E.js
416 ms
js_4htl2VgpzIj2B3aww45pGXUIUUlgqQT-NqvGPCiFjbI.js
213 ms
js_x6wjIiRxo-BcEpcukSnpp5rwfk5NnV3vEF4ZbMA1drM.js
298 ms
js_lk86mGsc_7d0x-SX6Ud-LKxKsexAbhP7FOi6YA5b-cc.js
285 ms
js_cz79PC54raE_VNE7EgjsrAzv4xiosmHNr_iu0mRqX8U.js
708 ms
jquery.dataTables.min.js
13 ms
dataTables.responsive.js
11 ms
clicktracker.js
402 ms
player_api
27 ms
ga.js
10 ms
__utm.gif
11 ms
www-widgetapi.js
4 ms
bg-header.png
252 ms
logo-magic-halo.png
161 ms
logo-magic.png
159 ms
background.jpg
156 ms
gppar16_eod1.jpg
751 ms
uvddkUU1DO_dmu_header.jpg
662 ms
ooD5wPFjZC_header_0.jpg
823 ms
SOI_Preloader_1.jpg
558 ms
bg-date-picker.jpg
191 ms
rss-icon-no-background.svg
228 ms
ooD5wPFjZC_icon.jpg
446 ms
IBkemx7KHn_CIG_icon.jpg
641 ms
cEl3FpriSW_icon.jpg
625 ms
uvddkUU1DO_dmu_icon.jpg
698 ms
bg-card-day.jpg
716 ms
0248_MTGSOI_EN_HRR.png
786 ms
4O4ngxojao_icon.jpg
731 ms
P2vYrUuBQJ_icon.jpg
836 ms
OP20160317_icon.jpg
894 ms
uiu9Xy79BC_icon.jpg
802 ms
bg-articles-last-slide.jpg
834 ms
EN_Announcing_Thumb_0.jpg
928 ms
jbLGM0xS8x_icon.jpg
874 ms
back-to-top.png
898 ms
where-to-buy-background.jpg
918 ms
wizard-of-the-coast-logo.png
904 ms
hasbro-logo.svg
944 ms
esrb-badge.png
1058 ms
MagicTheGathering
1035 ms
MagicTheGathering
1036 ms
wizards_magic
1041 ms
undefined
1039 ms
undefined
1040 ms
instagramLastPost
1039 ms
undefined
128 ms
12
1036 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
14 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
29 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
29 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
30 ms
icomoon.woff
913 ms
BELEREN-BOLD.woff
931 ms
PRmiXeptR36kaC0GEAetxjqR_3kx9_hJXbbyU8S6IN0.woff
27 ms
PRmiXeptR36kaC0GEAetxkCDe67GEgBv_HnyvHTfdew.woff
28 ms
PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff
28 ms
xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff
28 ms
PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff
28 ms
9185.js
12 ms
foresee-surveydef.js
928 ms
s
36 ms
u
30 ms
dailymtg.com 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
dailymtg.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
Page has valid source maps
dailymtg.com 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
Document doesn't have a valid hreflang
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 Dailymtg.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 Dailymtg.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.
dailymtg.com
Open Graph description is not detected on the main page of Daily MTG. 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: