Tools & Wizards About Us

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pressa.co.in

Mist Nozzle and Patio Heaters Manufacturer | S S Industries, Delhi

Page Load Speed

1.6 sec in total

First Response

274 ms

Resources Loaded

956 ms

Page Rendered

375 ms

About Website

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

S S Industries - Mist Nozzle, Patio Heaters & Perforated Items Manufacturer from Delhi, India

Visit pressa.co.in

Key Findings

We analyzed Pressa.co.in page load time and found that the first response time was 274 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

pressa.co.in performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

pressa.co.in

274 ms

www.pressa.co.in

251 ms

www.pressa.co.in

295 ms

dtstyle_43_min.css

19 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 Pressa.co.in, 25% (1 request) were made to Tdw.imimg.com. The less responsive or slowest element that took the longest time to load (295 ms) belongs to the original domain Pressa.co.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.3 kB (69%)

Content Size

92.0 kB

After Optimization

28.7 kB

  • HTML
  • CSS

In fact, the total size of Pressa.co.in main page is 92.0 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 10% of websites need less resources to load. HTML takes 77.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 63.3 kB

  • Original 77.8 kB
  • After minification 77.4 kB
  • After compression 14.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. 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 63.3 kB or 81% of the original size.

CSS Optimization

-0%

Potential reduce by 18 B

  • Original 14.2 kB
  • After minification 14.2 kB
  • After compression 14.2 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. Pressa.co.in has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • CSS

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

Network Requests Diagram

Accessibility Review

pressa.co.in accessibility score

64

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

pressa.co.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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

pressa.co.in 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 Pressa.co.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 Pressa.co.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

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