Tools & Wizards About Us
purti.net screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

purti.net

Purti | Edible Oil, Refined Oil Manufacturer & Supplier in Kolkata, India

Page Load Speed

8.6 sec in total

First Response

423 ms

Resources Loaded

7.6 sec

Page Rendered

564 ms

purti.net screenshot

About Website

Click here to check amazing Purti content for India. Otherwise, check out these important facts you probably never knew about purti.net

"Purti is a leading manufacturer, supplier & exporter of premium quality edible oil, refined oil, mustard oil used in hotels, for cooking various dishes.

Visit purti.net

Key Findings

We analyzed Purti.net page load time and found that the first response time was 423 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

purti.net performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value350 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.832

4/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

purti.net

423 ms

www.purti.net

1041 ms

73bd.css

205 ms

73bd.css

410 ms

dc1727b9d667a665a846755991090198.css

1203 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 79% of them (79 requests) were addressed to the original Purti.net, 10% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Purti.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.6 kB (3%)

Content Size

3.9 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Purti.net main page is 3.9 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 57.5 kB

  • Original 71.9 kB
  • After minification 63.7 kB
  • After compression 14.3 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 8.2 kB, which is 11% 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.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 50.1 kB

  • Original 3.4 MB
  • After minification 3.4 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. Purti images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 13.1 kB

  • Original 243.5 kB
  • After minification 243.5 kB
  • After compression 230.4 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

-13%

Potential reduce by 11.9 kB

  • Original 92.4 kB
  • After minification 92.4 kB
  • After compression 80.5 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. Purti.net needs all CSS files to be minified and compressed as it can save up to 11.9 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (59%)

Requests Now

80

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purti.net

purti.net

423 ms

www.purti.net

www.purti.net

1041 ms

73bd.css

73bd.css

205 ms

73bd.css

73bd.css

410 ms

dc1727b9d667a665a846755991090198.css

dc1727b9d667a665a846755991090198.css

1203 ms

5138932f6a2c94eea45a327330e492d5.css

5138932f6a2c94eea45a327330e492d5.css

1251 ms

style.css

style.css

739 ms

73nd.css

73nd.css

555 ms

73wa.js

73wa.js

817 ms

73wa.js

73wa.js

612 ms

style.css

style.css

747 ms

navigation.css

navigation.css

816 ms

brands.css

brands.css

922 ms

font-awesome.min.css

font-awesome.min.css

924 ms

bootstrap.min.css

bootstrap.min.css

42 ms

jquery.min.js

jquery.min.js

30 ms

bootstrap.min.js

bootstrap.min.js

55 ms

style.css

style.css

1025 ms

navigation.css

navigation.css

1022 ms

top-admin.css

top-admin.css

1104 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1293 ms

jquery.fancybox.js

jquery.fancybox.js

1248 ms

extns.js

extns.js

1249 ms

floara_content_theme.css

floara_content_theme.css

1288 ms

modernizr.custom.js

modernizr.custom.js

1378 ms

navigation.js

navigation.js

1388 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

1429 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

1430 ms

analytics.js

analytics.js

1473 ms

jquery-latest.js

jquery-latest.js

1478 ms

script.js

script.js

1560 ms

script1.js

script1.js

1572 ms

owl_002.css

owl_002.css

1631 ms

owl.css

owl.css

1631 ms

owl.js

owl.js

1656 ms

slick.css

slick.css

1662 ms

slick-theme.css

slick-theme.css

1743 ms

slick.js

slick.js

1755 ms

js

js

68 ms

responsiveslides.css

responsiveslides.css

1832 ms

responsiveslides.js

responsiveslides.js

1833 ms

addthis_widget.js

addthis_widget.js

30 ms

demo.js

demo.js

1838 ms

2016e3a7dfacf85410fbe3b02c291083.js

2016e3a7dfacf85410fbe3b02c291083.js

2616 ms

myscript.js

myscript.js

1523 ms

scripts.js

scripts.js

1391 ms

f6158785c0167f68b477c1596d2b73fb.js

f6158785c0167f68b477c1596d2b73fb.js

1891 ms

left-navigation.css

left-navigation.css

808 ms

font-awesome.min.css

font-awesome.min.css

796 ms

css

css

35 ms

css

css

53 ms

analytics.js

analytics.js

148 ms

purti-logo.png

purti-logo.png

393 ms

slide1.jpg

slide1.jpg

894 ms

slide2.jpg

slide2.jpg

1061 ms

slide3.jpg

slide3.jpg

894 ms

slide4.jpg

slide4.jpg

1177 ms

texture-corporate-light.jpg

texture-corporate-light.jpg

840 ms

Vanaspati.png

Vanaspati.png

1178 ms

Purti-Vanaspati-1.png

Purti-Vanaspati-1.png

1065 ms

pro-img1.png

pro-img1.png

1249 ms

Soyalite-1-ltr-pouch.png

Soyalite-1-ltr-pouch.png

1426 ms

pro-img2.png

pro-img2.png

1250 ms

Sunlife-1-ltr-pouch.png

Sunlife-1-ltr-pouch.png

1810 ms

pro-img3.png

pro-img3.png

1583 ms

Kacchi-ghani-1-ltr-pouch.png

Kacchi-ghani-1-ltr-pouch.png

1382 ms

pro-img4.png

pro-img4.png

1434 ms

Rizola-1-ltr-pouch-1.png

Rizola-1-ltr-pouch-1.png

1434 ms

welcome-bg.jpg

welcome-bg.jpg

1587 ms

lft-bg.png

lft-bg.png

1976 ms

rit-bg.png

rit-bg.png

1619 ms

inner-rit-bg.jpg

inner-rit-bg.jpg

1622 ms

line.jpg

line.jpg

1785 ms

manufacturing-banner.jpg

manufacturing-banner.jpg

1790 ms

quality-banner.jpg

quality-banner.jpg

1803 ms

Purti-BlogKachhi-Ghani-1568x882.jpg

Purti-BlogKachhi-Ghani-1568x882.jpg

1808 ms

Ricebran-Oil-Blog-1-1568x882.jpg

Ricebran-Oil-Blog-1-1568x882.jpg

1990 ms

purti-blog-img-1568x882.jpg

purti-blog-img-1568x882.jpg

1996 ms

footer-bg.jpg

footer-bg.jpg

1985 ms

PURTI-Logo-white.png

PURTI-Logo-white.png

1991 ms

spinner.gif

spinner.gif

1991 ms

34.png

34.png

2157 ms

collect

collect

39 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

79 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

273 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

280 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

278 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

278 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

279 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

279 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

277 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

280 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2057 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2080 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2244 ms

fbevents.js

fbevents.js

69 ms

collect

collect

254 ms

73bd.css

73bd.css

204 ms

73bd.css

73bd.css

204 ms

Accessibility Review

purti.net accessibility score

76

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

purti.net SEO score

89

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Purti.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 Purti.net main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

purti.net

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