995 ms in total
224 ms
687 ms
84 ms
Visit coriolis.io now to see the best up-to-date Coriolis content for United States and also check out these interesting facts you probably never knew about coriolis.io
A ship builder, outfitting and comparison tool for Elite Dangerous
Visit coriolis.ioWe analyzed Coriolis.io page load time and found that the first response time was 224 ms and then it took 771 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
coriolis.io performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value8.3 s
2/100
25%
Value7.6 s
26/100
10%
Value730 ms
41/100
30%
Value0.003
100/100
15%
Value8.4 s
39/100
10%
224 ms
198 ms
251 ms
Our browser made a total of 3 requests to load all elements on the main page. We found that all of those requests were addressed to Coriolis.io and no external sources were called. The less responsive or slowest element that took the longest time to load (251 ms) belongs to the original domain Coriolis.io.
Page size can be reduced by 49.3 kB (63%)
77.8 kB
28.5 kB
In fact, the total size of Coriolis.io main page is 77.8 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. Only 5% of websites need less resources to load. Javascripts take 52.9 kB which makes up the majority of the site volume.
Potential reduce by 921 B
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 921 B or 54% of the original size.
Potential reduce by 0 B
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. Coriolis images are well optimized though.
Potential reduce by 32.0 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 32.0 kB or 60% of the original size.
Potential reduce by 16.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. Coriolis.io needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 76% of the original size.
We found no issues to fix!
1
1
The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Coriolis. According to our analytics all requests are already optimized.
coriolis.io
224 ms
app.3cfc7083.css
198 ms
eurostile.2ee3b9b7.woff
251 ms
coriolis.io accessibility score
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
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.
coriolis.io 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
Missing source maps for large first-party JavaScript
coriolis.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Coriolis.io 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 Coriolis.io 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.
coriolis.io
Open Graph description is not detected on the main page of Coriolis. 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: