Tools & Wizards About Us
richo.pl screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

richo.pl

Home - RICHO

Page Load Speed

5 sec in total

First Response

347 ms

Resources Loaded

4.5 sec

Page Rendered

234 ms

richo.pl screenshot

About Website

Visit richo.pl now to see the best up-to-date RICHO content and also check out these interesting facts you probably never knew about richo.pl

RICHO POLSKA

Visit richo.pl

Key Findings

We analyzed Richo.pl page load time and found that the first response time was 347 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

richo.pl performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value2,690 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

richo.pl

347 ms

richo.pl

2591 ms

css

53 ms

style.min.css

118 ms

index.css

231 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 64% of them (36 requests) were addressed to the original Richo.pl, 9% (5 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Richo.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.6 kB (22%)

Content Size

787.2 kB

After Optimization

610.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Richo.pl main page is 787.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 503.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 70.7 kB

  • Original 91.6 kB
  • After minification 89.1 kB
  • After compression 20.9 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 70.7 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 2.2 kB

  • Original 108.6 kB
  • After minification 106.4 kB

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. RICHO images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 101.7 kB

  • Original 503.2 kB
  • After minification 503.2 kB
  • After compression 401.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 101.7 kB or 20% of the original size.

CSS Optimization

-2%

Potential reduce by 2.1 kB

  • Original 83.9 kB
  • After minification 83.8 kB
  • After compression 81.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. Richo.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (75%)

Requests Now

48

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

richo.pl

richo.pl

347 ms

richo.pl

richo.pl

2591 ms

css

css

53 ms

style.min.css

style.min.css

118 ms

index.css

index.css

231 ms

styles.css

styles.css

329 ms

front.min.css

front.min.css

331 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

344 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

345 ms

tablepress-combined.min.css

tablepress-combined.min.css

345 ms

avia-merged-styles-d6ae3f04afa5448cc2c198198d88cfd0---664adaeaa5ee9.css

avia-merged-styles-d6ae3f04afa5448cc2c198198d88cfd0---664adaeaa5ee9.css

599 ms

post-19.css

post-19.css

436 ms

jquery.min.js

jquery.min.js

551 ms

jquery-migrate.min.js

jquery-migrate.min.js

456 ms

front.min.js

front.min.js

455 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

456 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

544 ms

public.js

public.js

572 ms

js

js

79 ms

js

js

123 ms

index.js

index.js

566 ms

index.js

index.js

567 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

832 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

751 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

750 ms

api.js

api.js

74 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

750 ms

wp-polyfill.min.js

wp-polyfill.min.js

749 ms

index.js

index.js

749 ms

avia-footer-scripts-e3064c20ba6d65207e82b8fc5da3c49a---664adaeb1fb9e.js

avia-footer-scripts-e3064c20ba6d65207e82b8fc5da3c49a---664adaeb1fb9e.js

968 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

785 ms

gtm.js

gtm.js

124 ms

fbevents.js

fbevents.js

123 ms

universal.js

universal.js

167 ms

logo-richo-300x138.png

logo-richo-300x138.png

327 ms

b96d0d89-d0f4-467e-b441-191d57391002.png

b96d0d89-d0f4-467e-b441-191d57391002.png

756 ms

Pionowe-centrum-obr%C3%B3bcze-EVERRICHO-ER-VMC-300x200.jpg

Pionowe-centrum-obr%C3%B3bcze-EVERRICHO-ER-VMC-300x200.jpg

884 ms

UBM-11020RT-180x180.jpg

UBM-11020RT-180x180.jpg

282 ms

Tokarki-AERO-300x233.jpg

Tokarki-AERO-300x233.jpg

428 ms

OGC-1020%E5%8D%8A%E7%BD%A9%E5%90%AB%E5%9E%8B%E8%99%9F-300x225.jpg

OGC-1020%E5%8D%8A%E7%BD%A9%E5%90%AB%E5%9E%8B%E8%99%9F-300x225.jpg

430 ms

podajnik-BA-65-300x199.jpg

podajnik-BA-65-300x199.jpg

450 ms

Manipulator-180x180.jpg

Manipulator-180x180.jpg

497 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

47 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

53 ms

entypo-fontello.woff

entypo-fontello.woff

400 ms

recaptcha__en.js

recaptcha__en.js

26 ms

anchor

anchor

67 ms

styles__ltr.css

styles__ltr.css

17 ms

recaptcha__en.js

recaptcha__en.js

20 ms

8AXZAK1i6BpqK69J99oN0p3RtJQ1PGMK6D_RgjsU7ps.js

8AXZAK1i6BpqK69J99oN0p3RtJQ1PGMK6D_RgjsU7ps.js

71 ms

webworker.js

webworker.js

69 ms

logo_48.png

logo_48.png

56 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

34 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

34 ms

recaptcha__en.js

recaptcha__en.js

23 ms

Accessibility Review

richo.pl accessibility score

96

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

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

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

richo.pl SEO score

98

Search Engine Optimization Advices

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

richo.pl

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