6 sec in total
1.6 sec
2.8 sec
1.6 sec
Visit substance.media now to see the best up-to-date Substance content for United States and also check out these interesting facts you probably never knew about substance.media
Visit substance.mediaWe analyzed Substance.media page load time and found that the first response time was 1.6 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
substance.media performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.5 s
1/100
25%
Value7.6 s
26/100
10%
Value500 ms
58/100
30%
Value0.001
100/100
15%
Value8.6 s
37/100
10%
1575 ms
65 ms
57 ms
382 ms
356 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Substance.media, 84% (67 requests) were made to Cdn-images-1.medium.com and 8% (6 requests) were made to Cdn-static-1.medium.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Substance.media.
Page size can be reduced by 1.1 MB (18%)
5.9 MB
4.9 MB
In fact, the total size of Substance.media main page is 5.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. 85% 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 4.8 MB which makes up the majority of the site volume.
Potential reduce by 357.7 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 357.7 kB or 81% of the original size.
Potential reduce by 160.1 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. Substance images are well optimized though.
Potential reduce by 243.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 243.7 kB or 64% of the original size.
Potential reduce by 292.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. Substance.media needs all CSS files to be minified and compressed as it can save up to 292.6 kB or 84% of the original size.
Number of requests can be reduced by 4 (5%)
78
74
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Substance. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
substance.media
1575 ms
main-base.IFJUnFUw4SRQF1FfuINu0g.css
65 ms
main-base.bundle.m83G729yn7q7V7Milm_yFg.js
57 ms
icons.eR1AJ_5I759hGrg36Jtvbg.js
382 ms
ga.js
356 ms
stat
355 ms
1*Iby1opZbRZwNC4ZKMYnIUQ.png
460 ms
1*dp0wWxNT5vcWJnFIEuWYDA.png
495 ms
1*tVvMAOzb_EsvKspG6aaEnA.png
426 ms
1*UmRpJqlzRaifETIX105oUw.png
486 ms
1*wodHnThuNMIlh02dYpLFbQ.jpeg
426 ms
1*kR6SGqdGeitVtPeiGbTz0A.jpeg
427 ms
1*Fr6cuLaZNPIA__nD_JYnhw.jpeg
429 ms
1*th69kYhtPJqSxat55RnI-A.gif
482 ms
1*2VFBbfpaowRljfnRcpmkgQ.jpeg
481 ms
1*me1FgWRycGjB1TwWt6Ng1A.jpeg
430 ms
0*lgVdhMYtrO5RMcYF.jpeg
430 ms
1*aSRB04aIPruZ3-a9kdsPNg.jpeg
488 ms
1*Do5iSUifQ4N5ShjFhRMAxA.jpeg
481 ms
1*l2ueEjwebIp72bu5Ao-oXg.jpeg
482 ms
1*soWHp69uM2G_Rmku7Q_3bg.jpeg
484 ms
1*akw2KiVEdP2tAaBoIyYZ0w.gif
486 ms
1*NRlKFdZCoVlUeCcf-HQdUA.jpeg
487 ms
1*hL9FAavyzBAWW-FWWND4EQ.jpeg
494 ms
1*GDOIVTtYBNBIm3BCMw7h0g.png
492 ms
1*smNCsKgi5XZv0QQzW9nmjg.jpeg
489 ms
1*7GcdOIIXqFuTnDkFQoOhAQ.jpeg
488 ms
1*te40EDTJCvRTzySFfiv3vg.jpeg
495 ms
0*XmHZy3Vjxciwg97c.jpeg
491 ms
1*8mA91o10bXsdFbNlIbzdoQ.jpeg
497 ms
1*AXokI2-Ku6yIQTJp-3C2aQ.jpeg
493 ms
1*Rd5_STwYfXeqFo7Le7qAMg.jpeg
498 ms
1*EKmwmt2AXlzNrGofWGswFQ.jpeg
496 ms
1*rW15ziFvjW3RbupCeYro8Q.jpeg
503 ms
1*CechXE0f6tUy0CSJR4DGng.jpeg
499 ms
1*QN4-LDvJHKWFaqAJnA3SWA.png
669 ms
1*C7CiMXbjFaTueNmYLcoeuw.gif
623 ms
1*tSJcRWMxVmx2QMK3Tc_S7g.png
504 ms
1*Ty906QsvLr96x_oDpXqpEA.jpeg
500 ms
1*PTT7TIaFPWNs9CCMLpzHVA.jpeg
501 ms
1*tDaIF5YuzJ0te4g28s8uWg.gif
628 ms
1*k6wh_YyXxuCMHO59m37qZg.jpeg
507 ms
main-common-async.bundle.Jl1Gv1scggs1oLwpdlZwgQ.js
69 ms
medium-icons.d6MdYRMP1ChpRcny39OG0A.woff
39 ms
__utm.gif
37 ms
1*9E6lhxSbcN0nrQE1T7IFyw.gif
92 ms
1*anzOZcvQY68_zs3vNRdZjQ.jpeg
86 ms
1*OQ7fRpVYmFFH5RZOhsA0NQ.jpeg
91 ms
1*aMA_dDzt_VWSNMDARHRcMQ.jpeg
93 ms
1*aNKGpCyX3Jrym4hLeJX57Q.jpeg
88 ms
1*iLpSWWhI3wKYtwwJzrigbQ.jpeg
455 ms
main-misc-screens.bundle.Y8Bo8T52xbXMkyVkujRZ7Q.js
39 ms
1*yTXMshUzuFxdehf_Qbd-cw.png
138 ms
1*50siqbKXsB2bsdnx7dZ4aA.jpeg
139 ms
1*P0AknrjSR60PQpazQXyzXQ.jpeg
139 ms
1*quTgk7HiGvlKNR-NF-TATQ.jpeg
410 ms
1*vPbZI2W2CYAmhLQO0ccnPQ.jpeg
137 ms
1*w-GS8LIOihz4nUzeyaVzAg.jpeg
138 ms
1*MYo3eIx7Z0uPiE0MJnXTlw.jpeg
141 ms
1*c80VOsKde8_JwtJ909p3Tw.png
142 ms
1*58_4UzqhCgNkWl_rT1O6FQ.jpeg
140 ms
1*ixOfL11yFxqQzcg9m6xhPQ.png
145 ms
1*fRkGr1PUrlB_0_IYTghCXg.jpeg
143 ms
1*wDguml7PIemB4htoQps2GA.jpeg
143 ms
1*UjOeV6GdSqQIRUDw1OVKXw.jpeg
145 ms
1*IjrbDr4UcDdfppylZBbGdg.jpeg
142 ms
1*grk7MRlNDNFGCbXMf6pQTw.jpeg
142 ms
1*sd2lEZ5uFgHcoRSvAjYgnQ.jpeg
144 ms
1*QjEr5tPU1ABu5KFdbd55tw.jpeg
142 ms
1*IWm0_CTMW4cbTItk1kIN-Q.jpeg
142 ms
1*1wFU5nnpF3pZ5XNshxfIQg.jpeg
143 ms
1*ik7JNvZytvqrj6jhitmXzA.png
145 ms
1*uMBAIDwtIVPJmesixYeKpw.jpeg
141 ms
1*Z2aWqc7EN6nRzY74trnt_Q.jpeg
141 ms
1*rnyCPquWC0S50ZLAW35-vg.jpeg
142 ms
1*6qwMVoij3mOwaYofrHAwCA.gif
145 ms
1*aI-x5L5nvfW7R5I4GkcSAg.jpeg
140 ms
__utm.gif
50 ms
__utm.gif
50 ms
__utm.gif
50 ms
substance.media 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
[role]s do not have all required [aria-*] attributes
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.
substance.media 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
substance.media 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Substance.media 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 Substance.media 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.
substance.media
Open Graph data is detected on the main page of Substance. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: