Tools & Wizards About Us
censys.io screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

censys.io

Attack Surface Management and Threat Hunting Solutions | Censys

Page Load Speed

1.9 sec in total

First Response

43 ms

Resources Loaded

1.3 sec

Page Rendered

577 ms

censys.io screenshot

About Website

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.io

Key Findings

We analyzed Censys.io page load time and found that the first response time was 43 ms and then it took 1.9 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.

Performance Metrics

censys.io performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value4,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.213

58/100

15%

TTI (Time to Interactive)

Value24.4 s

0/100

10%

Network Requests Diagram

censys.io

43 ms

censys.com

311 ms

front-css.css

29 ms

new-flags.css

31 ms

fonts.min.css

27 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Censys.io, 68% (57 requests) were made to Censys.com and 6% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (643 ms) relates to the external source Go.censys.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.8 kB (26%)

Content Size

1.2 MB

After Optimization

909.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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 534.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 89.1 kB

  • Original 112.8 kB
  • After minification 111.9 kB
  • After compression 23.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 89.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 241 B

  • Original 534.0 kB
  • After minification 533.7 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.

JavaScript Optimization

-47%

Potential reduce by 234.4 kB

  • Original 500.1 kB
  • After minification 499.8 kB
  • After compression 265.7 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 234.4 kB or 47% of the original size.

CSS Optimization

-0%

Potential reduce by 48 B

  • Original 86.7 kB
  • After minification 86.7 kB
  • After compression 86.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. Censys.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 33 (42%)

Requests Now

79

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 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 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

censys.io

censys.io

43 ms

censys.com

censys.com

311 ms

front-css.css

front-css.css

29 ms

new-flags.css

new-flags.css

31 ms

fonts.min.css

fonts.min.css

27 ms

tingle.min.css

tingle.min.css

27 ms

style.min.css

style.min.css

34 ms

front-js.js

front-js.js

27 ms

bizible.js

bizible.js

20 ms

js

js

92 ms

forms2.min.js

forms2.min.js

184 ms

vanilla-marquee.min.js

vanilla-marquee.min.js

58 ms

tingle.min.js

tingle.min.js

57 ms

scripts.min.js

scripts.min.js

80 ms

gtm.js

gtm.js

97 ms

1010467.js

1010467.js

227 ms

s776ta4dv7d6.js

s776ta4dv7d6.js

214 ms

munchkin.js

munchkin.js

138 ms

axGRggPUZoY

axGRggPUZoY

216 ms

maxresdefault.webp

maxresdefault.webp

117 ms

dismiss.svg

dismiss.svg

43 ms

logo.svg

logo.svg

38 ms

menu-open.svg

menu-open.svg

45 ms

menu-close.svg

menu-close.svg

41 ms

headerburst.svg

headerburst.svg

38 ms

playpause-black.svg

playpause-black.svg

84 ms

btn-arrow-black.svg

btn-arrow-black.svg

84 ms

Search-Laptop-UI-Elements-940x1140.jpg

Search-Laptop-UI-Elements-940x1140.jpg

89 ms

ASM-Laptop-UI-Elements-50p-940x1140.jpg

ASM-Laptop-UI-Elements-50p-940x1140.jpg

106 ms

Censys-Internet-Map-With-Nodes-940x1140.jpg

Censys-Internet-Map-With-Nodes-940x1140.jpg

88 ms

statbar1-m.jpg

statbar1-m.jpg

110 ms

3x3-orange.svg

3x3-orange.svg

110 ms

burst.svg

burst.svg

108 ms

AB-In-Bev-170x170.png

AB-In-Bev-170x170.png

107 ms

Airbus-170x170.png

Airbus-170x170.png

107 ms

Almaviva-170x170.png

Almaviva-170x170.png

109 ms

Anomali-170x170.png

Anomali-170x170.png

117 ms

Autodesk-170x170.png

Autodesk-170x170.png

120 ms

Bloomberg-170x170.png

Bloomberg-170x170.png

119 ms

BlueVoyant-170x170.png

BlueVoyant-170x170.png

120 ms

Credit-Suisse-170x170.png

Credit-Suisse-170x170.png

118 ms

ebay-170x170.png

ebay-170x170.png

119 ms

Emerson-Electric-170x170.png

Emerson-Electric-170x170.png

130 ms

eset-170x170.png

eset-170x170.png

132 ms

Hitachi-170x170.png

Hitachi-170x170.png

131 ms

HSBC-Global-Services-UK-Ltd-170x170.png

HSBC-Global-Services-UK-Ltd-170x170.png

204 ms

icertis-170x170.png

icertis-170x170.png

132 ms

Incibe-170x170.png

Incibe-170x170.png

205 ms

Jackson-170x170.png

Jackson-170x170.png

205 ms

Microsoft-170x170.png

Microsoft-170x170.png

209 ms

NTT-170x170.png

NTT-170x170.png

210 ms

Okta-170x170.png

Okta-170x170.png

208 ms

Perspecta-Labs-170x170.png

Perspecta-Labs-170x170.png

202 ms

Rakuten-170x170.png

Rakuten-170x170.png

202 ms

Riot-Games-170x170.png

Riot-Games-170x170.png

202 ms

Secureworks-170x170.png

Secureworks-170x170.png

180 ms

Snap-Inc-170x170.png

Snap-Inc-170x170.png

175 ms

Summit-Utilities-170x170.png

Summit-Utilities-170x170.png

174 ms

Tandem-Cyber-170x170.png

Tandem-Cyber-170x170.png

171 ms

Trend-Micro-170x170.png

Trend-Micro-170x170.png

173 ms

Tokio-Marine-HCC-1-170x170.png

Tokio-Marine-HCC-1-170x170.png

138 ms

censys-cloud-secure-wide.jpg

censys-cloud-secure-wide.jpg

132 ms

twitter.png

twitter.png

132 ms

linkedin.png

linkedin.png

131 ms

chatbox.svg

chatbox.svg

113 ms

dtoggle.svg

dtoggle.svg

114 ms

munchkin.js

munchkin.js

75 ms

www-player.css

www-player.css

22 ms

www-embed-player.js

www-embed-player.js

51 ms

base.js

base.js

103 ms

getForm

getForm

643 ms

visitWebPage

visitWebPage

73 ms

wgarrowdown.png

wgarrowdown.png

36 ms

us.svg

us.svg

295 ms

ipv

ipv

32 ms

u

u

291 ms

xdc.js

xdc.js

258 ms

-0TfInu9ra9zkah2wyCD78KX7EDwI16Gf6-9m2UuzfU.js

-0TfInu9ra9zkah2wyCD78KX7EDwI16Gf6-9m2UuzfU.js

71 ms

embed.js

embed.js

34 ms

u

u

30 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

109 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

108 ms

Create

Create

106 ms

GenerateIT

GenerateIT

17 ms

Accessibility Review

censys.io accessibility score

93

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

censys.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

censys.io SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: