2.2 sec in total
146 ms
1.5 sec
531 ms
Click here to check amazing Docs Zoho content for India. Otherwise, check out these important facts you probably never knew about docs.zoho.com
signin
Visit docs.zoho.comWe analyzed Docs.zoho.com page load time and found that the first response time was 146 ms and then it took 2 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.
docs.zoho.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value6.4 s
10/100
25%
Value4.8 s
67/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value5.5 s
71/100
10%
146 ms
296 ms
73 ms
70 ms
66 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Docs.zoho.com, 39% (18 requests) were made to Zoho.com and 17% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (475 ms) relates to the external source Salesiq.zoho.com.
Page size can be reduced by 528.9 kB (34%)
1.6 MB
1.0 MB
In fact, the total size of Docs.zoho.com main page is 1.6 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. 45% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 56.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.1 kB or 82% of the original size.
Potential reduce by 189.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. Obviously, Docs Zoho needs image optimization as it can save up to 189.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 225.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 225.7 kB or 53% of the original size.
Potential reduce by 57.4 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. Docs.zoho.com needs all CSS files to be minified and compressed as it can save up to 57.4 kB or 84% of the original size.
Number of requests can be reduced by 13 (42%)
31
18
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs Zoho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
docs.zoho.com
146 ms
docs.zoho.com
296 ms
home
73 ms
70 ms
css
66 ms
product-home.css
27 ms
register.js
319 ms
jstz.min.js
37 ms
prd-common.js
54 ms
userinfo.js
46 ms
conversion.js
47 ms
jquery-plus-ui.js
79 ms
docs-mixpanelhandler.js
46 ms
docs-mixpanelTracker.js
45 ms
ga.js
62 ms
__utm.gif
13 ms
collect
59 ms
spacer.gif
41 ms
docs-management-software.png
192 ms
gtm.js
189 ms
product-common-sprite.png
75 ms
docs-sprite1.png
74 ms
docs-bg.jpg
152 ms
social-signin-sprite.png
74 ms
app-downloads-bg.jpg
152 ms
sync-part-bg.jpg
180 ms
docs_client_bg_1x.png
104 ms
float.ls
475 ms
94 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
222 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
256 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
292 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
342 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
359 ms
dazS1PrQQuCxC3iOAJFEJbfB31yxOzP-czbf6AAKCVo.ttf
359 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
359 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
358 ms
mixpanel-2-latest.min.js
87 ms
info
123 ms
product-icon-sprite.png
64 ms
80 ms
analytics.js
79 ms
51 ms
collect
17 ms
collect
18 ms
ga-audiences
34 ms
docs.zoho.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
docs.zoho.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
docs.zoho.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docs.zoho.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Docs.zoho.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.
docs.zoho.com
Open Graph description is not detected on the main page of Docs Zoho. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: