Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ior.poznan.pl

Strona główna | Instytut Ochrony Roślin - Państwowy Instytut Badawczy

Page Load Speed

6.2 sec in total

First Response

1.2 sec

Resources Loaded

4.5 sec

Page Rendered

599 ms

ior.poznan.pl screenshot

About Website

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

Serwis internetowy Instytutu Ochrony Roślin - Państwowego Instytutu Badawczego zawierający ważne informacje oraz aktualności dotyczące działalności instytutu.

Visit ior.poznan.pl

Key Findings

We analyzed Ior.poznan.pl page load time and found that the first response time was 1.2 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ior.poznan.pl performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value5,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.511

15/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

www.ior.poznan.pl

1163 ms

system_default.css

143 ms

style.css

294 ms

jquery.fancybox.min.css

390 ms

jquery.datatables.css

391 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that all of those requests were addressed to Ior.poznan.pl and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ior.poznan.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.6 kB (6%)

Content Size

3.0 MB

After Optimization

2.8 MB

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

HTML Optimization

-77%

Potential reduce by 55.6 kB

  • Original 72.3 kB
  • After minification 71.0 kB
  • After compression 16.7 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 55.6 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 107.6 kB

  • Original 2.7 MB
  • After minification 2.6 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. Ior images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 366 B

  • Original 154.5 kB
  • After minification 154.5 kB
  • After compression 154.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.

Requests Breakdown

Number of requests can be reduced by 15 (45%)

Requests Now

33

After Optimization

18

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

Accessibility Review

ior.poznan.pl accessibility score

90

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

Links do not have a discernible name

Best Practices

ior.poznan.pl best practices score

92

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

SEO Factors

ior.poznan.pl SEO score

89

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 doesn't use 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 Ior.poznan.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 Ior.poznan.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 Ior. 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: