2.2 sec in total
81 ms
1.2 sec
903 ms
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 81 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
io9.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value4.3 s
41/100
25%
Value46.5 s
0/100
10%
Value97,160 ms
0/100
30%
Value0.006
100/100
15%
Value123.1 s
0/100
10%
81 ms
270 ms
241 ms
396 ms
392 ms
Our browser made a total of 72 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% (10 requests) were made to F.kinja-static.com and 10% (7 requests) were made to X.kinja-static.com. The less responsive or slowest element that took the longest time to load (396 ms) relates to the external source I.kinja-img.com.
Page size can be reduced by 2.0 MB (60%)
3.3 MB
1.3 MB
In fact, the total size of Io9.com main page is 3.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 352.6 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 352.6 kB or 81% of the original size.
Potential reduce by 14.2 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. Io 9 images are well optimized though.
Potential reduce by 1.4 MB
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 1.4 MB or 71% of the original size.
Potential reduce by 178.6 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. Io9.com needs all CSS files to be minified and compressed as it can save up to 178.6 kB or 85% of the original size.
Number of requests can be reduced by 37 (66%)
56
19
The browser has sent 56 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 30 to 1 for JavaScripts and as a result speed up the page load time.
io9.gizmodo.com
81 ms
accountwithtoken
270 ms
veoxklw8coulpkai27fa.png
241 ms
vr0p4ag9tbylswlvz4ut.jpg
396 ms
gx473uzkd9saef7h6ylh.jpg
392 ms
ul1x1pxmpynlguyl2ekr.jpg
392 ms
blog-1019cc3ed05e6c7c829147e0f35d8890.css
39 ms
vendor.82a733c8519700ed8156.en-US.js
140 ms
FrontPage.40495021b941e0913bf8.en-US.js
220 ms
AdModule.30b645c961616ff5e252.en-US.js
65 ms
gpt.js
46 ms
amzn_ads.js
45 ms
f0kuqsfkt4xqbof77uvn.jpg
368 ms
szw7ul68rx2vqbqxhohh.jpg
368 ms
d16ra3i1yo1kkptnp3hu.jpg
367 ms
vr0p4ag9tbylswlvz4ut.jpg
370 ms
t0psa35obnpk592w7hjq.png
374 ms
gir9mxxwmkf32if4d8gs.jpg
373 ms
proxima_nova_cond_reg-webfont.woff
319 ms
proxima_nova_cond_sbold-webfont.woff
319 ms
pubads_impl_81.js
171 ms
bid
298 ms
elizabethserif-lightitalic-webfont.woff
236 ms
elizabethserif-italic-webfont.woff
236 ms
elizabethserif-bolditalic-webfont.woff
236 ms
elizabethserif-light-webfont.woff
236 ms
elizabethserif-regular-webfont.woff
237 ms
elizabethserif-bold-webfont.woff
237 ms
container.html
142 ms
rta.js
123 ms
6.a378ec1bc052554d2270.en-US.js
106 ms
3.d1dacb489c187db5ce57.en-US.js
106 ms
2.cf52dcc454bb8bf36e48.en-US.js
93 ms
chartbeat.js
92 ms
analytics.js
90 ms
quant.js
88 ms
controltag
90 ms
33330X1169095.skimlinks.js
86 ms
beacon.js
83 ms
DFP_Audience_Pixel;dc_seg=22540930;blog=io9;ord=3544038690160.96;postId=;tags=
84 ms
t0psa35obnpk592w7hjq.png
118 ms
DFP_Audience_Pixel;dc_seg=23702290;blog=io9;ord=2310010818764.5674;postId=;tags=;refer=
117 ms
m
103 ms
bid
45 ms
collect
28 ms
pixel;r=1962272052;a=p-d4P3FpSypJrlA;fpan=1;fpa=P0-525225230-1456746395355;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456746395355;tzo=-180;ref=;url=http%3A%2F%2Fio9.gizmodo.com%2F;ogl=title.io9%20-%20We%20come%20from%20the%20future%252E%2Ctype.blog%2Cimage.https%3A%2F%2Fi%252Ekinja-img%252Ecom%2Fgawker-media%2Fimage%2Fupload%2Fs---5Pxwo2n--%2Fc_fill%252Cfl_progre%2Curl.http%3A%2F%2Fio9%252Egizmodo%252Ecom%2Cdescription.We%20come%20from%20the%20future%252E%2Clocale.en_US%2Csite_name.io9
24 ms
ping
15 ms
14 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
61 ms
collect
28 ms
collect
96 ms
proxima_nova_cond_sbold_it-webfont.woff
36 ms
proxima_nova_cond_reg_it-webfont.woff
35 ms
link
56 ms
track.php
52 ms
optout_check
42 ms
get
81 ms
a.gif
345 ms
genericusersync.ashx
15 ms
generic
12 ms
generic
5 ms
bid
19 ms
ads
70 ms
7915939267665231411
62 ms
jload
56 ms
moatad.js
29 ms
ads
57 ms
osd.js
29 ms
mon
79 ms
jload
73 ms
vjuzj0ywxpfqrd2br8de.jpg
40 ms
dt
20 ms
io9.com 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
<frame> or <iframe> elements do not have a title
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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
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
Page is blocked from indexing
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: