4.1 sec in total
188 ms
2.2 sec
1.7 sec
Click here to check amazing Zss content. Otherwise, check out these important facts you probably never knew about zss.co.in
Visit zss.co.inWe analyzed Zss.co.in page load time and found that the first response time was 188 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
zss.co.in performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.1 s
2/100
25%
Value8.3 s
19/100
10%
Value1,110 ms
23/100
30%
Value0.149
76/100
15%
Value9.5 s
30/100
10%
188 ms
836 ms
184 ms
178 ms
247 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 93% of them (84 requests) were addressed to the original Zss.co.in, 4% (4 requests) were made to Maps.googleapis.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (836 ms) belongs to the original domain Zss.co.in.
Page size can be reduced by 304.8 kB (17%)
1.7 MB
1.4 MB
In fact, the total size of Zss.co.in main page is 1.7 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 57.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. This page needs HTML code to be minified as it can gain 28.2 kB, which is 44% 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 57.0 kB or 89% of the original size.
Potential reduce by 93.0 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. Zss images are well optimized though.
Potential reduce by 78.2 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 78.2 kB or 23% of the original size.
Potential reduce by 76.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. Zss.co.in needs all CSS files to be minified and compressed as it can save up to 76.6 kB or 38% of the original size.
Number of requests can be reduced by 37 (45%)
82
45
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
zss.co.in
188 ms
zss.co.in
836 ms
bootstrap.min.css
184 ms
icomoon.css
178 ms
remixicon.css
247 ms
magnifypopup.min.css
180 ms
odometer.min.css
178 ms
lightbox.min.css
181 ms
animation.min.css
241 ms
jqueru-ui-min.css
244 ms
swiper-bundle.min.css
244 ms
tipped.min.css
252 ms
app.css
312 ms
custom.css
302 ms
bg.css
306 ms
logo-dark.png
304 ms
logo-white.png
303 ms
1.jpg
476 ms
2.jpg
479 ms
embed
205 ms
modernizr.min.js
362 ms
jquery.min.js
473 ms
bootstrap.min.js
473 ms
sal.min.js
471 ms
backtotop.min.js
473 ms
magnifypopup.min.js
473 ms
jquery.countdown.min.js
489 ms
odometer.min.js
490 ms
isotop.min.js
491 ms
imageloaded.min.js
490 ms
lightbox.min.js
509 ms
paralax.min.js
533 ms
paralax-scroll.min.js
549 ms
jquery-ui.min.js
553 ms
swiper-bundle.min.js
591 ms
svg-inject.min.js
548 ms
vivus.min.js
590 ms
tipped.min.js
607 ms
smooth-scroll.min.js
566 ms
isInViewport.jquery.min.js
443 ms
app.js
452 ms
shape-13.png
477 ms
dark-shape-13.png
474 ms
shape-12.png
478 ms
js
42 ms
shape-09.png
444 ms
dark-shape-09.png
438 ms
shape-04.png
450 ms
about-03.webp
449 ms
search.js
5 ms
geometry.js
7 ms
main.js
14 ms
shape-03.png
446 ms
shape-38.png
427 ms
shape-37.png
444 ms
shape-04.png
443 ms
course-01.jpg
455 ms
css2
62 ms
course-02.jpg
466 ms
course-03.jpg
510 ms
iso1.jpg
458 ms
iso2.jpg
459 ms
shape-13.png
340 ms
shape-02.png
346 ms
shape-04.png
402 ms
icomoon4478.ttf
403 ms
remixicondf6d.woff
415 ms
shape-05.png
448 ms
testimonial-01.png
454 ms
testimonial-02.png
448 ms
testimonial-03.png
446 ms
testimonial-04.png
480 ms
c3.jpg
462 ms
c10.jpg
457 ms
c5.jpg
460 ms
c4.jpg
420 ms
c9.jpg
425 ms
c11.jpg
448 ms
c2.jpg
448 ms
c8.jpg
459 ms
c6.jpg
457 ms
c7.jpg
431 ms
c1.jpg
433 ms
shape-41.png
467 ms
dark-shape-41.png
462 ms
shape-19.png
460 ms
shape-20.png
460 ms
bg-image-1.svg
448 ms
shape-1.png
452 ms
BG-3.png
486 ms
zss.co.in 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
<frame> or <iframe> elements do not have a title
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
Heading elements are not in a sequentially-descending order
zss.co.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
zss.co.in SEO score
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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zss.co.in 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 Zss.co.in 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.
zss.co.in
Open Graph description is not detected on the main page of Zss. 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: