Tools & Wizards About Us
omnires.pl screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

omnires.pl

OMNIRES

Page Load Speed

3.2 sec in total

First Response

32 ms

Resources Loaded

2.8 sec

Page Rendered

317 ms

omnires.pl screenshot

About Website

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

OMNIRES to polska firma o globalnym zasięgu, której pasją od ponad 30 lat jest tworzenie wysokiej jakości produktów i doświadczeń tak, by umożliwiać innym kreację przemyślanych, inspirujących do życia...

Visit omnires.pl

Key Findings

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

Performance Metrics

omnires.pl performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.638

9/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

omnires.pl

32 ms

702 ms

mtq5voj.css

146 ms

all.min.css

32 ms

jquery-ui.min.css

23 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Omnires.pl, 74% (28 requests) were made to Omnires.com and 13% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Omnires.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.5 kB (14%)

Content Size

739.1 kB

After Optimization

635.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Omnires.pl main page is 739.1 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. 35% of websites need less resources to load. Javascripts take 512.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 77.2 kB

  • Original 94.0 kB
  • After minification 93.8 kB
  • After compression 16.8 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 77.2 kB or 82% of the original size.

JavaScript Optimization

-0%

Potential reduce by 280 B

  • Original 512.4 kB
  • After minification 512.4 kB
  • After compression 512.1 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

-20%

Potential reduce by 26.1 kB

  • Original 132.7 kB
  • After minification 132.7 kB
  • After compression 106.6 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. Omnires.pl needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

32

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

omnires.pl

omnires.pl

32 ms

702 ms

mtq5voj.css

mtq5voj.css

146 ms

all.min.css

all.min.css

32 ms

jquery-ui.min.css

jquery-ui.min.css

23 ms

layout.css

layout.css

533 ms

homepage.css

homepage.css

346 ms

blocks.css

blocks.css

435 ms

app.js

app.js

105 ms

p.css

p.css

38 ms

cookieconsent.css

cookieconsent.css

39 ms

logo_omnires_old.svg

logo_omnires_old.svg

319 ms

ic_lang_globe_6.svg

ic_lang_globe_6.svg

317 ms

ic_close_black.svg

ic_close_black.svg

318 ms

ic_menu_search.svg

ic_menu_search.svg

318 ms

ic_menu_favourite.svg

ic_menu_favourite.svg

443 ms

ic_menu_user.svg

ic_menu_user.svg

445 ms

ic_fb_2.svg

ic_fb_2.svg

602 ms

ic_google.svg

ic_google.svg

633 ms

menu_logo_omnires_mobile.svg

menu_logo_omnires_mobile.svg

636 ms

10dbfa0432c9d9c4c4b2cd866f08.webp

10dbfa0432c9d9c4c4b2cd866f08.webp

901 ms

59385800d3640e653248e0b2d9b1.webp

59385800d3640e653248e0b2d9b1.webp

1109 ms

48fa5773ab994acc2e5190e24846.webp

48fa5773ab994acc2e5190e24846.webp

1055 ms

6d5ace23e8643edfb3f823e22469.webp

6d5ace23e8643edfb3f823e22469.webp

1189 ms

ic_pin.svg

ic_pin.svg

948 ms

banner-arrow.svg

banner-arrow.svg

995 ms

ic_arrow_down_white.svg

ic_arrow_down_white.svg

1218 ms

ic_instagram.svg

ic_instagram.svg

1263 ms

ic_facebook.svg

ic_facebook.svg

1309 ms

ic_pinterest3.svg

ic_pinterest3.svg

1387 ms

ic_youtube.svg

ic_youtube.svg

1433 ms

ic_linkedin.svg

ic_linkedin.svg

1522 ms

ic_spotify.svg

ic_spotify.svg

1229 ms

ic-archiproducts.svg

ic-archiproducts.svg

1558 ms

d

d

9 ms

d

d

8 ms

d

d

28 ms

d

d

29 ms

Accessibility Review

omnires.pl accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

omnires.pl SEO score

100

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

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

omnires.pl

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