Tools & Wizards About Us
dzaine.in screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

dzaine.in

dZaine.in • Bespoke eCommerce design and development.

Page Load Speed

7.1 sec in total

First Response

1.5 sec

Resources Loaded

5.1 sec

Page Rendered

537 ms

dzaine.in screenshot

About Website

Visit dzaine.in now to see the best up-to-date DZaine content and also check out these interesting facts you probably never knew about dzaine.in

dZaine.in is an eCommerce design and development studio based in Pune, and we'd love to help you meet your customers online. Let's begin.

Visit dzaine.in

Key Findings

We analyzed Dzaine.in page load time and found that the first response time was 1.5 sec 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.

Performance Metrics

dzaine.in performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.05

99/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

dzaine.in

1532 ms

theme.min.css

213 ms

style.css

211 ms

style.min.css

220 ms

frontend-lite.min.css

294 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that all of those requests were addressed to Dzaine.in and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dzaine.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 841.6 kB (65%)

Content Size

1.3 MB

After Optimization

454.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dzaine.in main page is 1.3 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 79.3 kB

  • Original 95.1 kB
  • After minification 95.1 kB
  • After compression 15.9 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 79.3 kB or 83% of the original size.

Image Optimization

-75%

Potential reduce by 759.5 kB

  • Original 1.0 MB
  • After minification 250.8 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, DZaine needs image optimization as it can save up to 759.5 kB or 75% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 186 B

  • Original 149.9 kB
  • After minification 149.8 kB
  • After compression 149.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 2.7 kB

  • Original 40.5 kB
  • After minification 38.3 kB
  • After compression 37.8 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. Dzaine.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (73%)

Requests Now

44

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DZaine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dzaine.in

dzaine.in

1532 ms

theme.min.css

theme.min.css

213 ms

style.css

style.css

211 ms

style.min.css

style.min.css

220 ms

frontend-lite.min.css

frontend-lite.min.css

294 ms

post-5.css

post-5.css

222 ms

elementor-icons.min.css

elementor-icons.min.css

228 ms

swiper.min.css

swiper.min.css

435 ms

frontend-lite.min.css

frontend-lite.min.css

442 ms

post-2.css

post-2.css

464 ms

post-34.css

post-34.css

467 ms

post-145.css

post-145.css

471 ms

fontawesome.min.css

fontawesome.min.css

531 ms

solid.min.css

solid.min.css

657 ms

script.custom.js

script.custom.js

665 ms

jquery.min.js

jquery.min.js

836 ms

jquery-migrate.min.js

jquery-migrate.min.js

692 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

699 ms

animations.min.css

animations.min.css

749 ms

hello-frontend.min.js

hello-frontend.min.js

921 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

1051 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

922 ms

webpack.runtime.min.js

webpack.runtime.min.js

939 ms

frontend-modules.min.js

frontend-modules.min.js

1060 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1068 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1142 ms

wp-polyfill.min.js

wp-polyfill.min.js

1144 ms

hooks.min.js

hooks.min.js

1181 ms

i18n.min.js

i18n.min.js

1307 ms

frontend.min.js

frontend.min.js

1290 ms

waypoints.min.js

waypoints.min.js

1315 ms

core.min.js

core.min.js

1361 ms

frontend.min.js

frontend.min.js

1394 ms

elements-handlers.min.js

elements-handlers.min.js

1432 ms

jquery.sticky.min.js

jquery.sticky.min.js

1534 ms

logoOrange.png

logoOrange.png

829 ms

heroGraphic.png

heroGraphic.png

1027 ms

buyOnline.png

buyOnline.png

912 ms

onlineCustomers.png

onlineCustomers.png

765 ms

succulent.png

succulent.png

874 ms

photograph.png

photograph.png

1016 ms

email.png

email.png

1012 ms

sportsLogosFeatured.png

sportsLogosFeatured.png

1400 ms

indianDigitizerFeatured.png

indianDigitizerFeatured.png

1344 ms

popCulturedFeatured.png

popCulturedFeatured.png

1412 ms

outfit-v2-latin-regular.woff

outfit-v2-latin-regular.woff

1232 ms

outfit-v2-latin-600.woff

outfit-v2-latin-600.woff

1269 ms

Accessibility Review

dzaine.in accessibility score

90

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

dzaine.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

dzaine.in SEO score

100

Search Engine Optimization Advices

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

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

Social Sharing Optimization

dzaine.in

Open Graph data is detected on the main page of DZaine. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: