1.8 sec in total
755 ms
830 ms
213 ms
Click here to check amazing Substack content for United States. Otherwise, check out these important facts you probably never knew about substack.net
Visit substack.netWe analyzed Substack.net page load time and found that the first response time was 755 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
substack.net performance score
name
value
score
weighting
Value1.7 s
92/100
10%
Value1.7 s
99/100
25%
Value2.3 s
99/100
10%
Value1,160 ms
22/100
30%
Value0
100/100
15%
Value3.2 s
95/100
10%
755 ms
97 ms
98 ms
97 ms
64 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 63% of them (15 requests) were addressed to the original Substack.net, 8% (2 requests) were made to Scratch.substack.net and 8% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (755 ms) belongs to the original domain Substack.net.
Page size can be reduced by 360.0 kB (75%)
482.1 kB
122.1 kB
In fact, the total size of Substack.net main page is 482.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. CSS take 242.9 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.9 kB or 69% of the original size.
Potential reduce by 132.3 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 132.3 kB or 66% of the original size.
Potential reduce by 201.8 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. Substack.net needs all CSS files to be minified and compressed as it can save up to 201.8 kB or 83% of the original size.
Number of requests can be reduced by 3 (16%)
19
16
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Substack. 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 JavaScripts and as a result speed up the page load time.
substack.net
755 ms
style.css
97 ms
substack_header_letters.png
98 ms
substack.png
97 ms
github.png
64 ms
npm.png
60 ms
gittip.png
177 ms
twitter.png
183 ms
soundcloud.png
184 ms
facebook.png
176 ms
lanyrd.png
176 ms
youtube.png
279 ms
electrolize.ttf
94 ms
a8VLnap86pA
122 ms
circuit_small.jpg
145 ms
workspace_small.jpg
146 ms
krona.ttf
114 ms
www-embed-player-vflZsBgOl.css
74 ms
www-embed-player.js
95 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
49 ms
ad_status.js
45 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
99 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
110 ms
bundle.js
50 ms
substack.net 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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
substack.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
substack.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Substack.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Substack.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
substack.net
Open Graph description is not detected on the main page of Substack. 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: