4.1 sec in total
206 ms
3.6 sec
323 ms
Welcome to simondrake.com homepage info - get ready to check Simon Drake best content right away, or after learning these important things about simondrake.com
Simon Drake
Visit simondrake.comWe analyzed Simondrake.com page load time and found that the first response time was 206 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.
simondrake.com performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.4 s
92/100
25%
Value15.4 s
1/100
10%
Value22,530 ms
0/100
30%
Value0.231
54/100
15%
Value73.5 s
0/100
10%
206 ms
89 ms
178 ms
176 ms
177 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 25% of them (23 requests) were addressed to the original Simondrake.com, 18% (17 requests) were made to Encore.scdn.co and 15% (14 requests) were made to Jnn-pa.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source D1rx8vrt2hn1hc.cloudfront.net.
Page size can be reduced by 119.3 kB (2%)
7.4 MB
7.3 MB
In fact, the total size of Simondrake.com main page is 7.4 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. Only a small number of websites need less resources to load. Javascripts take 6.6 MB which makes up the majority of the site volume.
Potential reduce by 12.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. 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 12.4 kB or 72% of the original size.
Potential reduce by 69.8 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. Obviously, Simon Drake needs image optimization as it can save up to 69.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 32.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.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. Simondrake.com has all CSS files already compressed.
Number of requests can be reduced by 21 (30%)
70
49
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simon Drake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
simondrake.com
206 ms
layout-lrr.css
89 ms
mediaqueries.css
178 ms
jquery.1.9.0.min.js
176 ms
jquery-mobilemenu.min.js
177 ms
widgets.js
44 ms
framework.css
100 ms
navi.css
176 ms
anchor.png
1446 ms
investing-in-space.jpg
1153 ms
MBS9FdqYc5U
108 ms
lunar-resources-registry.png
1442 ms
anchor.png
283 ms
Simon-Drake-Logo.png
255 ms
space-commodities-exchange-stocks.png
288 ms
twitter-space.png
97 ms
linkedin-space.jpg
89 ms
citywire.png
254 ms
spotify-simon-drake.png
259 ms
telegraph-UK-news-space-investing.jpg
1146 ms
The-Times.png
282 ms
financial-times-investing-in-space-special.png
914 ms
moneyweb-space-investor.png
921 ms
Swissquote-space-investing-article.png
923 ms
new-space-people.png
1144 ms
delano-logo-luxembourg-english.png
1145 ms
DGLR_Luft-und-Raumfahrt.png
1145 ms
simon-drake-space-resources.png
1443 ms
email-me-png100.png
1145 ms
SRgVizDpR3k
228 ms
ndl2R2-iWXI
123 ms
bdLVi1CpX8Y
121 ms
WKo6UloSLho
122 ms
_223Dg76epg
121 ms
zIC0vrv6fmw
257 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
30 ms
a-a5p9irn
207 ms
settings
168 ms
www-player.css
48 ms
www-embed-player.js
80 ms
base.js
185 ms
bundle-fe4bf26e8f1fc7f41ec9.css
134 ms
ProfileEpisodeContainer-05657deca692c8b246ad.css
765 ms
bundle-24d11e50d617e41caacf.js
2709 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
656 ms
anchor.png
1343 ms
ad_status.js
1006 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
586 ms
embed.js
237 ms
5e33e9cce24910c0.jpeg
622 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
183 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
716 ms
CircularSp-Book-3f73da7d35bd81c706bce7bbb84964de.woff
1327 ms
CircularSp-Bold-856afe2da4ba4e61239b129e2c16d633.woff
1536 ms
CircularSp-Arab-Bold-47ca0fd648a183136981f28d0218cef6.woff
1539 ms
CircularSp-Arab-Black-9dda323448d48d7e6cabf84d2df7dc11.woff
1541 ms
CircularSp-Arab-Book-1cd31794cbdd53724469ba03e8573dba.woff
1540 ms
CircularSp-Hebr-Bold-caa03e4cb8690e726ef1625c7d91a7a5.woff
1555 ms
CircularSp-Hebr-Black-f52613a9d541248805af1d0bb33102f8.woff
1540 ms
CircularSp-Hebr-Book-d8209975eafc81a9499df8401a339ddd.woff
1541 ms
CircularSp-Cyrl-Bold-7e54bccaf45728c472079785d5cd4519.woff
1649 ms
CircularSp-Cyrl-Black-b4305d9bf82554f631d2636c3ef90c54.woff
1553 ms
CircularSp-Cyrl-Book-6f078f781ee313e298ad8997fd1ffe3d.woff
1549 ms
CircularSp-Grek-Bold-53bb923248ba22cf5554bbe5f434c5c8.woff
1551 ms
CircularSp-Grek-Black-49883536c1a3bfc688235ce40572731d.woff
1550 ms
CircularSp-Grek-Book-c9de2c0741586c1ab7b6e95541fc7807.woff
1550 ms
CircularSp-Deva-Bold-a218ed3bd8e480245847933a79f4ebfb.woff
1553 ms
CircularSp-Deva-Black-f1dca2ee660273063af0316d4b7da438.woff
1555 ms
CircularSp-Deva-Book-e1dc3d746b24723f8d3dadb314b97705.woff
1554 ms
Create
801 ms
Create
799 ms
Create
800 ms
Create
801 ms
Create
797 ms
Create
1301 ms
Create
1412 ms
Create
1412 ms
id
439 ms
simondrake
598 ms
polyfills-3b821eda8863adcc4a4b.js
115 ms
runtime-a697c5a1ae32bd7e4d42.js
614 ms
modules.20f98d7498a59035a762.js
615 ms
main-fd9ef5eb169057cda26d.js
616 ms
_app-88bf420a57d49e33be53.js
616 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
616 ms
_buildManifest.js
615 ms
_ssgManifest.js
616 ms
GenerateIT
123 ms
GenerateIT
125 ms
GenerateIT
120 ms
GenerateIT
127 ms
GenerateIT
123 ms
GenerateIT
125 ms
simondrake.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
simondrake.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
simondrake.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Simondrake.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 Simondrake.com main page’s claimed encoding is iso-8859-1. 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.
simondrake.com
Open Graph description is not detected on the main page of Simon Drake. 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: