2.9 sec in total
67 ms
1.7 sec
1.1 sec
Click here to check amazing Censys content for China. Otherwise, check out these important facts you probably never knew about censys.io
Attack Surface Management and Threat Hunting solutions powered by the most comprehensive dataset of internet intelligence.
Visit censys.ioWe analyzed Censys.io page load time and found that the first response time was 67 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
censys.io performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value5.4 s
20/100
25%
Value22.9 s
0/100
10%
Value49,840 ms
0/100
30%
Value0.262
47/100
15%
Value66.1 s
0/100
10%
67 ms
18 ms
29 ms
44 ms
52 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 51% of them (38 requests) were addressed to the original Censys.io, 8% (6 requests) were made to Youtube-nocookie.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (421 ms) belongs to the original domain Censys.io.
Page size can be reduced by 472.7 kB (38%)
1.2 MB
756.2 kB
In fact, the total size of Censys.io main page is 1.2 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. 70% of websites need less resources to load. Images take 601.4 kB which makes up the majority of the site volume.
Potential reduce by 56.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 56.0 kB or 78% of the original size.
Potential reduce by 32.6 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. Censys images are well optimized though.
Potential reduce by 72.6 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 72.6 kB or 41% of the original size.
Potential reduce by 311.5 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. Censys.io needs all CSS files to be minified and compressed as it can save up to 311.5 kB or 82% of the original size.
Number of requests can be reduced by 35 (49%)
71
36
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Censys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
censys.io
67 ms
fonts.min.css
18 ms
tingle.min.css
29 ms
style.min.css
44 ms
jquery.min.js
52 ms
jquery-migrate.min.js
51 ms
v2.js
142 ms
5851803.js
141 ms
vanilla-marquee.min.js
91 ms
tingle.min.js
91 ms
scripts.min.js
95 ms
gtm.js
226 ms
s776ta4dv7d6.js
298 ms
axGRggPUZoY
157 ms
maxresdefault.webp
209 ms
dismiss.svg
48 ms
logo.svg
40 ms
menu-open.svg
39 ms
menu-close.svg
48 ms
mag.svg
44 ms
headerburst.svg
45 ms
playpause-black.svg
55 ms
playbtn.svg
134 ms
ASM-Demo-Thumbnail.png
197 ms
chaos.gif
417 ms
burst.svg
147 ms
abinbev-ogo-170x170.png
147 ms
aircall-logo-170x170.png
196 ms
autodesk-logo-170x170.png
196 ms
CISA-logo-170x170.png
199 ms
cisco-logo-170x170.png
198 ms
Falabella-logo-170x171.png
207 ms
Google-Customer-Logo-170x170.png
208 ms
icertis-logo-170x170.png
208 ms
microsoft-logo-170x171.png
273 ms
nu-logo-170x171.png
274 ms
okta-logo-170x170.png
312 ms
university-of-louisville-logo-170x170.png
312 ms
homebigD.jpg
361 ms
3x3.svg
322 ms
homeHalf-940x1140.jpg
414 ms
twitter.png
413 ms
linkedin.png
412 ms
chatbox.svg
421 ms
json
202 ms
5851803.js
230 ms
fb.js
229 ms
5851803.js
286 ms
www-player.css
189 ms
www-embed-player.js
230 ms
base.js
320 ms
fetch-polyfill.js
169 ms
analytics.js
176 ms
uwt.js
203 ms
insight.min.js
169 ms
6si.min.js
196 ms
json
94 ms
collect
310 ms
getuidj
333 ms
c.6sc.co
332 ms
ipv6.6sc.co
359 ms
css
232 ms
collect
414 ms
Y-zeT9jJ33tCNYTX0Kw8-3I-ogsAM9wZgys9W8554e8.js
179 ms
embed.js
51 ms
img.gif
290 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
205 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
206 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
204 ms
adsct
243 ms
adsct
244 ms
Create
148 ms
ga-audiences
68 ms
30 ms
GenerateIT
14 ms
censys.io 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
Links do not have a discernible name
censys.io 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
Page has valid source maps
censys.io 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
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 Censys.io 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 Censys.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.
censys.io
Open Graph data is detected on the main page of Censys. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: