Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 39

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

haerson.pl

Nowoczesne maszyny do mycia podłogi, szorowarki do podłóg

Page Load Speed

5.2 sec in total

First Response

489 ms

Resources Loaded

4.4 sec

Page Rendered

272 ms

haerson.pl screenshot

About Website

Welcome to haerson.pl homepage info - get ready to check Haerson best content for Poland right away, or after learning these important things about haerson.pl

Oferujemy urządzenia czyszczące i maszyny do mycia podłóg, szorowarki i myjki do podłóg, maszyny czyszczące dla firm i instytucji | Sprzedaż i serwis w całej Polsce

Visit haerson.pl

Key Findings

We analyzed Haerson.pl page load time and found that the first response time was 489 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

haerson.pl performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.466

19/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

haerson.pl

489 ms

www.haerson.pl

1339 ms

jceutilities-217.css

124 ms

style.css

335 ms

style.css

335 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 91% of them (105 requests) were addressed to the original Haerson.pl, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Haerson.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.3 kB (23%)

Content Size

1.5 MB

After Optimization

1.1 MB

In fact, the total size of Haerson.pl main page is 1.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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 57.4 kB

  • Original 67.8 kB
  • After minification 53.2 kB
  • After compression 10.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 14.6 kB, which is 22% 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.4 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 104.1 kB

  • Original 1.1 MB
  • After minification 1.0 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. Haerson images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 136.5 kB

  • Original 225.0 kB
  • After minification 217.5 kB
  • After compression 88.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 136.5 kB or 61% of the original size.

CSS Optimization

-81%

Potential reduce by 39.3 kB

  • Original 48.8 kB
  • After minification 35.2 kB
  • After compression 9.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. Haerson.pl needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (42%)

Requests Now

110

After Optimization

64

The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haerson. 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 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

haerson.pl accessibility score

39

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

haerson.pl 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

SEO Factors

haerson.pl 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

    PL

  • Language Claimed

    PL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haerson.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and it matches the claimed language. Our system also found out that Haerson.pl 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 Haerson. 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: