5.8 sec in total
204 ms
3.5 sec
2 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 204 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
zss.co.in performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value9.8 s
0/100
25%
Value7.7 s
25/100
10%
Value320 ms
77/100
30%
Value0.002
100/100
15%
Value8.6 s
37/100
10%
204 ms
286 ms
247 ms
182 ms
188 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 97% of them (84 requests) were addressed to the original Zss.co.in, 1% (1 request) were made to Google.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Zss.co.in.
Page size can be reduced by 289.3 kB (18%)
1.6 MB
1.4 MB
In fact, the total size of Zss.co.in 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. 50% 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 52.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 52.2 kB or 23% of the original size.
Potential reduce by 87.2 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 87.2 kB or 41% of the original size.
Number of requests can be reduced by 34 (43%)
79
45
The browser has sent 79 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 22 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
zss.co.in
204 ms
zss.co.in
286 ms
bootstrap.min.css
247 ms
icomoon.css
182 ms
remixicon.css
188 ms
magnifypopup.min.css
184 ms
odometer.min.css
183 ms
lightbox.min.css
196 ms
animation.min.css
366 ms
jqueru-ui-min.css
370 ms
swiper-bundle.min.css
368 ms
tipped.min.css
362 ms
app.css
547 ms
custom.css
437 ms
bg.css
543 ms
logo-dark.png
540 ms
logo-white.png
543 ms
1.jpg
722 ms
2.jpg
779 ms
embed
210 ms
modernizr.min.js
779 ms
jquery.min.js
844 ms
bootstrap.min.js
871 ms
sal.min.js
810 ms
backtotop.min.js
900 ms
magnifypopup.min.js
955 ms
jquery.countdown.min.js
958 ms
odometer.min.js
960 ms
isotop.min.js
1028 ms
imageloaded.min.js
1027 ms
lightbox.min.js
1080 ms
paralax.min.js
1135 ms
paralax-scroll.min.js
1141 ms
jquery-ui.min.js
1140 ms
swiper-bundle.min.js
1367 ms
svg-inject.min.js
1267 ms
vivus.min.js
1266 ms
tipped.min.js
1394 ms
smooth-scroll.min.js
1324 ms
isInViewport.jquery.min.js
1154 ms
app.js
1285 ms
shape-13.png
1282 ms
dark-shape-13.png
1333 ms
shape-12.png
1331 ms
js
49 ms
shape-09.png
1304 ms
dark-shape-09.png
1224 ms
shape-04.png
1278 ms
about-03.webp
1335 ms
shape-03.png
1338 ms
shape-38.png
1274 ms
shape-37.png
1200 ms
shape-04.png
1225 ms
course-01.jpg
1453 ms
css2
64 ms
course-02.jpg
1414 ms
icomoon4478.ttf
1279 ms
remixicondf6d.woff
1333 ms
course-03.jpg
1283 ms
iso1.jpg
1390 ms
iso2.jpg
1515 ms
shape-13.png
1336 ms
shape-02.png
1313 ms
shape-04.png
1317 ms
shape-05.png
1332 ms
testimonial-01.png
1427 ms
testimonial-02.png
1364 ms
testimonial-03.png
1359 ms
testimonial-04.png
1370 ms
c3.jpg
1387 ms
c10.jpg
1482 ms
c5.jpg
1439 ms
c4.jpg
1359 ms
c9.jpg
1359 ms
c11.jpg
1362 ms
c2.jpg
1437 ms
c8.jpg
1472 ms
c6.jpg
1459 ms
c7.jpg
1404 ms
c1.jpg
1373 ms
shape-41.png
1351 ms
dark-shape-41.png
1429 ms
shape-19.png
1486 ms
shape-20.png
1466 ms
bg-image-1.svg
1406 ms
shape-1.png
1349 ms
BG-3.png
1348 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: