Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pisf.pl

PISF - POLSKI INSTYTUT SZTUKI FILMOWEJ

Page Load Speed

5.4 sec in total

First Response

246 ms

Resources Loaded

4.8 sec

Page Rendered

441 ms

pisf.pl screenshot

About Website

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

Strona internetowa PISF - Polskiego Instytutu Sztuki Filmowej

Visit pisf.pl

Key Findings

We analyzed Pisf.pl page load time and found that the first response time was 246 ms and then it took 5.2 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

pisf.pl performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.954

3/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

pisf.pl

246 ms

463 ms

cookieconsent.js

35 ms

cookieconsent.css

51 ms

js

74 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 83% of them (88 requests) were addressed to the original Pisf.pl, 8% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Pisf.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (11%)

Content Size

9.6 MB

After Optimization

8.5 MB

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

HTML Optimization

-85%

Potential reduce by 92.2 kB

  • Original 108.2 kB
  • After minification 92.2 kB
  • After compression 16.0 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 16.0 kB, which is 15% 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 92.2 kB or 85% of the original size.

Image Optimization

-10%

Potential reduce by 872.9 kB

  • Original 9.1 MB
  • After minification 8.2 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. PISF images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 87.1 kB

  • Original 277.9 kB
  • After minification 277.9 kB
  • After compression 190.9 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 87.1 kB or 31% of the original size.

CSS Optimization

-9%

Potential reduce by 11.3 kB

  • Original 122.2 kB
  • After minification 122.2 kB
  • After compression 111.0 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. Pisf.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (66%)

Requests Now

94

After Optimization

32

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

Accessibility Review

pisf.pl accessibility score

86

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

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

pisf.pl best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pisf.pl SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Pisf.pl 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 Pisf.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 PISF. 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: