Report Summary

  • 77

    Performance

    Renders faster than
    84% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

dukepipes.com

No1 uPVC pipes manufacturers company in Gujarat, India - DukePipes

Page Load Speed

3.3 sec in total

First Response

774 ms

Resources Loaded

2.3 sec

Page Rendered

269 ms

About Website

Welcome to dukepipes.com homepage info - get ready to check Duke Pipes best content right away, or after learning these important things about dukepipes.com

No1 DukePipes uPVC pipes manufacturers company in Gujarat, India are manufacturing best uPVC Casing or Column Pipe, ASTM, HDPE sprinkler and SWR pipes.

Visit dukepipes.com

Key Findings

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

Performance Metrics

dukepipes.com performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.22

57/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

Network Requests Diagram

dukepipes.com

774 ms

mobile-menu.css

197 ms

icon

46 ms

css

58 ms

css

61 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 70% of them (47 requests) were addressed to the original Dukepipes.com, 15% (10 requests) were made to Demo.phpgang.com and 6% (4 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Dukepipes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (57%)

Content Size

5.5 MB

After Optimization

2.4 MB

In fact, the total size of Dukepipes.com main page is 5.5 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. 55% of websites need less resources to load. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 48.1 kB

  • Original 53.6 kB
  • After minification 27.4 kB
  • After compression 5.5 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 26.3 kB, which is 49% 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 48.1 kB or 90% of the original size.

Image Optimization

-57%

Potential reduce by 3.1 MB

  • Original 5.4 MB
  • After minification 2.3 MB

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, Duke Pipes needs image optimization as it can save up to 3.1 MB or 57% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 19.7 kB

  • Original 97.2 kB
  • After minification 97.2 kB
  • After compression 77.5 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 19.7 kB or 20% of the original size.

CSS Optimization

-60%

Potential reduce by 13.1 kB

  • Original 21.8 kB
  • After minification 21.8 kB
  • After compression 8.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. Dukepipes.com needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

51

After Optimization

33

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

Accessibility Review

dukepipes.com accessibility score

60

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

dukepipes.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dukepipes.com SEO score

82

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dukepipes.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dukepipes.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

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