Tools & Wizards About Us
naty.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

naty.com

Shop Eco Diapers | 10% off first order | Eco by Naty

Page Load Speed

3.9 sec in total

First Response

292 ms

Resources Loaded

2.7 sec

Page Rendered

930 ms

naty.com screenshot

About Website

Visit naty.com now to see the best up-to-date Naty content for Russia and also check out these interesting facts you probably never knew about naty.com

0% oil based plastic on skin - Our diapers are environmentally friendly and have 100% plant based materials on your baby's skin.

Visit naty.com

Key Findings

We analyzed Naty.com page load time and found that the first response time was 292 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

naty.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value25.8 s

0/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,760 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.132

81/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

292 ms

site.min.js

97 ms

tp.widget.bootstrap.min.js

65 ms

j.php

79 ms

events.js

119 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 69% of them (33 requests) were addressed to the original Naty.com, 4% (2 requests) were made to Dev.visualwebsiteoptimizer.com and 2% (1 request) were made to Cdn.curalate.com. The less responsive or slowest element that took the longest time to load (868 ms) relates to the external source Static.site24x7rum.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 373.6 kB (17%)

Content Size

2.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Naty.com main page is 2.1 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.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 52.9 kB

  • Original 69.6 kB
  • After minification 69.5 kB
  • After compression 16.7 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 52.9 kB or 76% of the original size.

Image Optimization

-23%

Potential reduce by 297.3 kB

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

JavaScript Optimization

-2%

Potential reduce by 15.0 kB

  • Original 749.7 kB
  • After minification 749.7 kB
  • After compression 734.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

-16%

Potential reduce by 8.4 kB

  • Original 51.7 kB
  • After minification 51.7 kB
  • After compression 43.3 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. Naty.com needs all CSS files to be minified and compressed as it can save up to 8.4 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (52%)

Requests Now

44

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

292 ms

site.min.js

site.min.js

97 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

65 ms

j.php

j.php

79 ms

events.js

events.js

119 ms

collect.js

collect.js

67 ms

css

css

85 ms

gtmCommon.js

gtmCommon.js

83 ms

gtmGa4js.js

gtmGa4js.js

81 ms

snippet.js

snippet.js

86 ms

fonts.css

fonts.css

114 ms

style.css

style.css

116 ms

uc.js

uc.js

172 ms

powr.js

powr.js

86 ms

v.gif

v.gif

13 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

37 ms

jquery-ui.min.js

jquery-ui.min.js

76 ms

slick.js

slick.js

37 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

82 ms

jquery.validate.min.js

jquery.validate.min.js

81 ms

jquery.zoom.min.js

jquery.zoom.min.js

80 ms

app.js

app.js

225 ms

smartorderrefill.js

smartorderrefill.js

80 ms

dwanalytics-22.2.js

dwanalytics-22.2.js

80 ms

dwac-21.7.js

dwac-21.7.js

224 ms

gretel.min.js

gretel.min.js

81 ms

sensor.js

sensor.js

372 ms

gtm.js

gtm.js

247 ms

naty-logo.png

naty-logo.png

190 ms

worry-free-icon.png

worry-free-icon.png

150 ms

subscription-icon.png

subscription-icon.png

208 ms

free-shipping-icon.png

free-shipping-icon.png

208 ms

Product%20Banner%20Diaper%20DESKTOP%20copy.png

Product%20Banner%20Diaper%20DESKTOP%20copy.png

208 ms

Product%20Banner%20Pants%20DESKTOP.png

Product%20Banner%20Pants%20DESKTOP.png

220 ms

Product%20Banner%20Wipes%20DESKTOP.png

Product%20Banner%20Wipes%20DESKTOP.png

216 ms

naty-footer-logo-humblegrp.png

naty-footer-logo-humblegrp.png

216 ms

payment-methods_PayPal.png

payment-methods_PayPal.png

215 ms

payment-methods_Mastercard.png

payment-methods_Mastercard.png

244 ms

payment-methods_Visa.png

payment-methods_Visa.png

213 ms

payment-methods_Amex.png

payment-methods_Amex.png

231 ms

payment-methods_Diners-Club.png

payment-methods_Diners-Club.png

239 ms

payment-methods_Discover.png

payment-methods_Discover.png

238 ms

shipping-methods_UPS.png

shipping-methods_UPS.png

243 ms

FuturaStdBook.woff

FuturaStdBook.woff

550 ms

FuturaStdMedium.woff

FuturaStdMedium.woff

558 ms

naty-icons.woff

naty-icons.woff

480 ms

track_page_view

track_page_view

50 ms

site24x7rum-min.js

site24x7rum-min.js

868 ms

Accessibility Review

naty.com accessibility score

72

Accessibility Issues

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-*] attributes do not match their roles

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

naty.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

naty.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

Social Sharing Optimization

naty.com

Open Graph description is not detected on the main page of Naty. 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: