Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

purensure.net

Manufacturer of RO Skid & Kent Water Purifier by Pure & Sure Water Technologies, Ahmedabad

Page Load Speed

979 ms in total

First Response

96 ms

Resources Loaded

536 ms

Page Rendered

347 ms

purensure.net screenshot

About Website

Click here to check amazing Pure N Sure content. Otherwise, check out these important facts you probably never knew about purensure.net

Pure & Sure Water Technologies - Manufacturer of RO Skid, Kent Water Purifier & RO Pump from Ahmedabad, Gujarat, India

Visit purensure.net

Key Findings

We analyzed Purensure.net page load time and found that the first response time was 96 ms and then it took 883 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

purensure.net performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

purensure.net

96 ms

www.purensure.net

69 ms

www.purensure.net

253 ms

dtstyle_42_min.css

22 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original Purensure.net, 25% (1 request) were made to Tdw.imimg.com. The less responsive or slowest element that took the longest time to load (253 ms) belongs to the original domain Purensure.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.6 kB (66%)

Content Size

78.7 kB

After Optimization

27.1 kB

In fact, the total size of Purensure.net main page is 78.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. HTML takes 64.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.6 kB

  • Original 64.7 kB
  • After minification 64.3 kB
  • After compression 13.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. 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 51.6 kB or 80% of the original size.

CSS Optimization

-0%

Potential reduce by 26 B

  • Original 14.0 kB
  • After minification 14.0 kB
  • After compression 14.0 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. Purensure.net has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pure N Sure. According to our analytics all requests are already optimized.

Accessibility Review

purensure.net accessibility score

48

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.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

purensure.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

purensure.net SEO score

85

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

High

Tap targets are not sized appropriately

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 Purensure.net 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 Purensure.net 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

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