Tools & Wizards About Us
pfleiderer.pl screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

pfleiderer.pl

Sustainable Wood-Based Panels and Solutions | Pfleiderer

Page Load Speed

2.9 sec in total

First Response

167 ms

Resources Loaded

2.3 sec

Page Rendered

390 ms

pfleiderer.pl screenshot

About Website

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

Sustainable wood-based panels, HPL and decorative surfaces for furniture, interior design and construction. High quality, innovative designs – discover Pfleiderer’s full range.

Visit pfleiderer.pl

Key Findings

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

Performance Metrics

pfleiderer.pl performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.681

8/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

pfleiderer.pl

167 ms

pfleiderer.pl

332 ms

189 ms

js

64 ms

gtm.js

117 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 75% of them (47 requests) were addressed to the original Pfleiderer.pl, 5% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pfleiderer.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.8 kB (18%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pfleiderer.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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 49.0 kB

  • Original 62.8 kB
  • After minification 47.0 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 15.7 kB, which is 25% 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 49.0 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 65.6 kB

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

JavaScript Optimization

-56%

Potential reduce by 159.2 kB

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

Requests Breakdown

Number of requests can be reduced by 23 (43%)

Requests Now

54

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pfleiderer.pl

pfleiderer.pl

167 ms

pfleiderer.pl

pfleiderer.pl

332 ms

189 ms

js

js

64 ms

gtm.js

gtm.js

117 ms

df6b9343cf.js

df6b9343cf.js

45 ms

b2c_responsive.css

b2c_responsive.css

436 ms

addons_responsive.css

addons_responsive.css

345 ms

analyticsmediatorcreator.js

analyticsmediatorcreator.js

342 ms

adsbygoogle.js

adsbygoogle.js

109 ms

generatedVariables.js

generatedVariables.js

259 ms

all_responsive.js

all_responsive.js

1023 ms

addons_responsive.js

addons_responsive.js

549 ms

24903019.js

24903019.js

502 ms

js

js

88 ms

analytics.js

analytics.js

46 ms

collect

collect

94 ms

collect

collect

23 ms

ga-audiences

ga-audiences

101 ms

fbevents.js

fbevents.js

96 ms

arrow-left-gold.svg

arrow-left-gold.svg

158 ms

flag_pl.svg

flag_pl.svg

156 ms

flag_en.svg

flag_en.svg

158 ms

flag_ru.svg

flag_ru.svg

154 ms

pfleiderer-logo.svg

pfleiderer-logo.svg

263 ms

duropal-logo.svg

duropal-logo.svg

273 ms

thermopal-logo.svg

thermopal-logo.svg

277 ms

star-icon.svg

star-icon.svg

234 ms

decor-scanner-icon-mobile.svg

decor-scanner-icon-mobile.svg

275 ms

mobile-menu-icon.svg

mobile-menu-icon.svg

316 ms

right-arrow-icon.svg

right-arrow-icon.svg

343 ms

arrow-left-icon.svg

arrow-left-icon.svg

356 ms

message-icon.svg

message-icon.svg

357 ms

book-icon.svg

book-icon.svg

359 ms

mood-stories-logo.svg

mood-stories-logo.svg

395 ms

new-icon.svg

new-icon.svg

447 ms

BANERY-ULTRAFIT-PFL27.jpg

BANERY-ULTRAFIT-PFL27.jpg

934 ms

thumbnail-baner-B-660x440.jpg

thumbnail-baner-B-660x440.jpg

621 ms

baner-strona-www.jpg

baner-strona-www.jpg

538 ms

ok-kafelki.jpg

ok-kafelki.jpg

579 ms

kafelek-akademia-pfleiderer.jpg

kafelek-akademia-pfleiderer.jpg

785 ms

contact-form-bcg.webp

contact-form-bcg.webp

641 ms

znajdz-nas-icon-white.svg

znajdz-nas-icon-white.svg

685 ms

mail-icon-white.svg

mail-icon-white.svg

696 ms

partnerzy-icon-white.svg

partnerzy-icon-white.svg

723 ms

pfl-footer-logo.svg

pfl-footer-logo.svg

743 ms

durpal-footer-logo.svg

durpal-footer-logo.svg

786 ms

thermopal-footer-logo.svg

thermopal-footer-logo.svg

802 ms

PFL-IKONA-FACEBOOK-W.svg

PFL-IKONA-FACEBOOK-W.svg

827 ms

PFL-IKONA-YOUTUBE-W.svg

PFL-IKONA-YOUTUBE-W.svg

846 ms

PFL-IKONA-INSTAGRAM-W.svg

PFL-IKONA-INSTAGRAM-W.svg

890 ms

PFL-IKONA-PINTEREST-W.svg

PFL-IKONA-PINTEREST-W.svg

889 ms

arrow-top-right-gold.svg

arrow-top-right-gold.svg

882 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

1083 ms

leadflows.js

leadflows.js

785 ms

24903019.js

24903019.js

514 ms

fb.js

fb.js

449 ms

24903019.js

24903019.js

550 ms

collectedforms.js

collectedforms.js

710 ms

Montserrat-SemiBold.ttf

Montserrat-SemiBold.ttf

1049 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

1047 ms

Montserrat-Light.ttf

Montserrat-Light.ttf

818 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

821 ms

Accessibility Review

pfleiderer.pl accessibility score

83

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

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

pfleiderer.pl best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pfleiderer.pl SEO score

89

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

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

pfleiderer.pl

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