2.6 sec in total
72 ms
662 ms
1.9 sec
Click here to check amazing Io 9 content for United States. Otherwise, check out these important facts you probably never knew about io9.com
We come from the future.
Visit io9.comWe analyzed Io9.com page load time and found that the first response time was 72 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
io9.com performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value4.8 s
31/100
25%
Value17.8 s
0/100
10%
Value15,030 ms
0/100
30%
Value0.04
99/100
15%
Value45.7 s
0/100
10%
72 ms
250 ms
122 ms
140 ms
136 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Io9.com, 14% (6 requests) were made to F.kinja-static.com and 9% (4 requests) were made to Kinja.com. The less responsive or slowest element that took the longest time to load (491 ms) relates to the external source I.kinja-img.com.
Page size can be reduced by 375.2 kB (30%)
1.3 MB
876.3 kB
In fact, the total size of Io9.com main page is 1.3 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. 55% of websites need less resources to load. Images take 719.1 kB which makes up the majority of the site volume.
Potential reduce by 375.0 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 375.0 kB or 86% 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. Io 9 images are well optimized though.
Potential reduce by 190 B
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.
Number of requests can be reduced by 6 (16%)
37
31
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Io 9. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
io9
72 ms
js
250 ms
analytics.js
122 ms
matomo.js
140 ms
lux.js
136 ms
9772940b1d9b2dbee6ecb14cdc26eaf3.jpg
367 ms
ccpa.js
345 ms
accountwithtoken
344 ms
ecefb3b4a8aee41d5421f3d4becf626f.jpg
338 ms
0fd0530984d0af620758737a1e3efe78.jpg
338 ms
22106f091a49c6068b9ca36359d90f73.jpg
342 ms
fe04e33ee6943e32995577daf40b9700.jpg
351 ms
8f8ad32bc7a5a76a4ff0888a11dd0ae1.jpg
341 ms
545374f846661f75c077a22b4a139f25.jpg
351 ms
71f0ccd614cda3083947feb773276924.jpg
351 ms
471eb0828d37afe21828416849538b36.jpg
350 ms
0c3ef4fe31b243b93e0faf5b8f10e584.jpg
349 ms
8e9a221602db377e012d47232ed5568a.jpg
350 ms
9cfd38af8a5c5e049dc878ede6e74bac.jpg
353 ms
3c0d1bf139979546eb0379c3df4dba1c.jpg
390 ms
6b6e3ff38376bd172d57bccd16e48b79.jpg
390 ms
bc40a560b5d53e10216d096ddb56c848.jpg
387 ms
138df2cf4c49df7c14e2eee369f941cb.jpg
389 ms
4b96fbc264a5a3d73671f0f97cd898ca.jpg
390 ms
eb283724d64e897316c0325c54d29acf.jpg
394 ms
5c53d2b5a0c102240b5070b0219fc9ea.jpg
401 ms
0bb3da986a608dcd3b6d929e73071974.jpg
401 ms
9376e82f9e4fcce201af110f6f0ffbd4.jpg
395 ms
e83d611b550c96526a8466d41db5054e.jpg
406 ms
2b025f031120bf968d2416e9e61113d5.jpg
402 ms
56e5044b7297823f24701394703b72b1.jpg
397 ms
ad0b2e29294086b7e70607f139f47290.jpg
408 ms
eca5dcf8e5b980ca02459df127afb402.jpg
409 ms
2d6b04d9026e4193f91a51fe6fe0f098.jpg
491 ms
a94dff6066baad4fd047dc1bb7570dac.jpg
404 ms
3f8d4e9e0885512e986468e29dc44984.jpg
489 ms
matomo.php
147 ms
roboto_condensed_ext_reg-webfont.woff
205 ms
roboto_condensed_ext_light-webfont.woff
293 ms
roboto_condensed_ext_bold-webfont.woff2
208 ms
roboto_condensed_ext_bold_it-webfont.woff2
206 ms
roboto_condensed_ext_reg_it-webfont.woff
292 ms
roboto_condensed_ext_light_it-webfont.woff
293 ms
configs.php
87 ms
io9.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
io9.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
io9.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Io9.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 Io9.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.
io9.com
Open Graph data is detected on the main page of Io 9. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: