2 sec in total
63 ms
1.2 sec
750 ms
Click here to check amazing Zscaler content for India. Otherwise, check out these important facts you probably never knew about zscaler.com
Zscaler, the zero trust cybersecurity leader, accelerates digital transformation with fast, secure connections between users, devices and apps over any network.
Visit zscaler.comWe analyzed Zscaler.com page load time and found that the first response time was 63 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.
zscaler.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.4 s
0/100
25%
Value8.1 s
21/100
10%
Value2,570 ms
4/100
30%
Value0.001
100/100
15%
Value16.4 s
5/100
10%
63 ms
44 ms
107 ms
38 ms
55 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Zscaler.com, 4% (3 requests) were made to Cdn.cookielaw.org and 1% (1 request) were made to Cdn.intellimize.co. The less responsive or slowest element that took the longest time to load (462 ms) belongs to the original domain Zscaler.com.
Page size can be reduced by 379.2 kB (76%)
499.5 kB
120.3 kB
In fact, the total size of Zscaler.com main page is 499.5 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. 45% of websites need less resources to load. HTML takes 462.8 kB which makes up the majority of the site volume.
Potential reduce by 379.1 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 379.1 kB or 82% of the original size.
Potential reduce by 89 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 40 (49%)
82
42
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zscaler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
zscaler.com
63 ms
zscaler.com
44 ms
www.zscaler.com
107 ms
117186981.js
38 ms
OtAutoBlock.js
55 ms
otSDKStub.js
65 ms
a9a273f44ba2b0c1.css
86 ms
88605379f801a6d3.css
127 ms
65b2cfa02816a9e9.css
79 ms
345f4163936959f7.css
139 ms
39dc5916e674dd7c.css
115 ms
6cebce83ced742f7.css
114 ms
544bfdbe148a2c06.css
168 ms
0a6faa6d1f9c8d2e.css
112 ms
c689cf67063d137d.css
192 ms
c910b9d3faea484a.css
209 ms
beec612b0534fa07.css
182 ms
5eef57a36340ae78.css
194 ms
e1f7f7d5ee9208b2.css
213 ms
polyfills-78c92fac7aa8fdd8.js
299 ms
1211.641acbb5193c454d.js
316 ms
1354.51864c9315139c37.js
317 ms
5192.b01af0b1566e0a65.js
297 ms
5267.dea4ff25c014c234.js
317 ms
2883.7cd49355efa8041a.js
297 ms
4979.87898132e7066c60.js
319 ms
9435.4a9f42021faccfe1.js
322 ms
12.95e57d3dd6e08abd.js
331 ms
9801.3b3237bfd452dfee.js
322 ms
791.e8919a226bfe7d52.js
334 ms
9901.6d7f089f5295baa8.js
351 ms
8900.9fd7001725b53986.js
321 ms
webpack-5238fb59e2cd513a.js
378 ms
framework-aec4381329cec0e4.js
389 ms
main-d4b326de8ea81632.js
380 ms
_app-7cb44808d00f6bc3.js
421 ms
4612-3783f202055153ba.js
412 ms
5403-24b4d1e45a6ee2a6.js
430 ms
3666-0828d08981c03e61.js
400 ms
5609-ff89b508a72b19d9.js
450 ms
6451-2070459b48abdbef.js
415 ms
%5B%5B...slug%5D%5D-5f880985c12eebe7.js
415 ms
3e894970-e3e9-4783-85e9-7c38eedbfbbf.json
26 ms
_buildManifest.js
361 ms
_ssgManifest.js
358 ms
location
44 ms
image
391 ms
image
381 ms
image
392 ms
image
385 ms
image
340 ms
image
325 ms
image
330 ms
image
328 ms
image
332 ms
image
322 ms
image
239 ms
image
250 ms
image
308 ms
image
274 ms
image
332 ms
image
256 ms
image
257 ms
image
352 ms
image
275 ms
image
363 ms
image
293 ms
image
392 ms
image
322 ms
image
356 ms
image
348 ms
image
350 ms
image
384 ms
image
400 ms
image
366 ms
image
373 ms
image
411 ms
image
412 ms
image
456 ms
image
419 ms
image
404 ms
image
429 ms
image
434 ms
image
418 ms
image
462 ms
zscaler.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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
zscaler.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
zscaler.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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zscaler.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 Zscaler.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.
zscaler.com
Open Graph data is detected on the main page of Zscaler. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: