4.7 sec in total
750 ms
2.1 sec
1.8 sec
Visit simonwillison.com now to see the best up-to-date Simon Willison content and also check out these interesting facts you probably never knew about simonwillison.com
Visit simonwillison.comWe analyzed Simonwillison.com page load time and found that the first response time was 750 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.
simonwillison.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.4 s
67/100
25%
Value2.4 s
98/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.3 s
99/100
10%
750 ms
22 ms
33 ms
25 ms
74 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Simonwillison.com, 13% (4 requests) were made to Blog.simonwillison.net and 13% (4 requests) were made to 33.media.tumblr.com. The less responsive or slowest element that took the longest time to load (750 ms) relates to the external source Blog.simonwillison.net.
Page size can be reduced by 543.6 kB (33%)
1.7 MB
1.1 MB
In fact, the total size of Simonwillison.com main page is 1.7 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. 60% of websites need less resources to load. Images take 903.4 kB which makes up the majority of the site volume.
Potential reduce by 147.4 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 46.5 kB, which is 25% 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 147.4 kB or 80% of the original size.
Potential reduce by 16.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. Simon Willison images are well optimized though.
Potential reduce by 339.9 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 339.9 kB or 65% of the original size.
Potential reduce by 40.2 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. Simonwillison.com needs all CSS files to be minified and compressed as it can save up to 40.2 kB or 77% of the original size.
Number of requests can be reduced by 10 (40%)
25
15
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simon Willison. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
blog.simonwillison.net
750 ms
pre_tumblelog.js
22 ms
main-min.css
33 ms
tumblelog_post_message_queue.js
25 ms
jquery.min.js
74 ms
main-min.js
73 ms
index.js
67 ms
avatar_1af962f74269_128.png
237 ms
tumblr_inline_mrgtpaFkyu1qz4rgp.png
334 ms
like_iframe.html
227 ms
tumblr_mra8lvlDfr1sn2ef4o1_1280.jpg
232 ms
tumblr_inline_mrgtlqZyOM1qz4rgp.png
219 ms
tumblr_inline_mrgtnsnBQT1qz4rgp.png
218 ms
impixu
218 ms
impixu
118 ms
analytics.html
116 ms
Gibson-Regular-webfont.woff
27 ms
Gibson-SemiBold-webfont.woff
26 ms
8EN1DX6pvX3m1fBD9AETcHqcA
7 ms
login_check.html
26 ms
wired-owls-small.jpg
209 ms
fort-clonque.jpg
228 ms
avatar_1af962f74269_40.png
29 ms
iframe_logo.png
21 ms
devfort-group.jpg
214 ms
rapid-3.36.js
49 ms
rapidworker-1.2.js
46 ms
ga.js
53 ms
analytics.js
80 ms
cs.js
76 ms
__utm.gif
11 ms
cedexis.radar.js
4 ms
simonwillison.com 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.
simonwillison.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
simonwillison.com 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 Simonwillison.com 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 Simonwillison.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.
simonwillison.com
Open Graph description is not detected on the main page of Simon Willison. 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: