Tools & Wizards About Us
wiecznepiora.pl screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

wiecznepiora.pl

Pióra wieczne i kulkowe, długopisy Parker z grawerem - Pióroteka

Page Load Speed

4.7 sec in total

First Response

663 ms

Resources Loaded

3.7 sec

Page Rendered

306 ms

wiecznepiora.pl screenshot

About Website

Welcome to wiecznepiora.pl homepage info - get ready to check Wieczne Piora best content right away, or after learning these important things about wiecznepiora.pl

Wysokiej jakości pióra wieczne, kulkowe i długopisy marek takich jak Parker czy Waterman w przystępnych cenach. Zapraszamy do zapoznania się z naszą ofertą!

Visit wiecznepiora.pl

Key Findings

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

Performance Metrics

wiecznepiora.pl performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value24.0 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value3,650 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value1.099

1/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

wiecznepiora.eu

663 ms

MzY6MjE4OjUuMjQuMjE.css

323 ms

main.269cce96f2dbf5d2886a.min.js

978 ms

pl_PL.js

475 ms

user.js

474 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wiecznepiora.pl, 12% (7 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (978 ms) relates to the external source Wiecznepiora.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 630.0 kB (55%)

Content Size

1.2 MB

After Optimization

522.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wiecznepiora.pl main page is 1.2 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. HTML takes 653.7 kB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 618.0 kB

  • Original 653.7 kB
  • After minification 279.6 kB
  • After compression 35.6 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 374.1 kB, which is 57% 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 618.0 kB or 95% of the original size.

Image Optimization

-5%

Potential reduce by 6.6 kB

  • Original 128.0 kB
  • After minification 121.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. Wieczne Piora images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.3 kB

  • Original 310.8 kB
  • After minification 310.8 kB
  • After compression 305.4 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

-0%

Potential reduce by 0 B

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

Requests Breakdown

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

Requests Now

44

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wiecznepiora.eu

wiecznepiora.eu

663 ms

MzY6MjE4OjUuMjQuMjE.css

MzY6MjE4OjUuMjQuMjE.css

323 ms

main.269cce96f2dbf5d2886a.min.js

main.269cce96f2dbf5d2886a.min.js

978 ms

pl_PL.js

pl_PL.js

475 ms

user.js

user.js

474 ms

front-api-1.4.0.min.js

front-api-1.4.0.min.js

523 ms

js

js

55 ms

sm_front.js

sm_front.js

631 ms

css

css

33 ms

font-awesome.min.css

font-awesome.min.css

151 ms

gtm.js

gtm.js

86 ms

1px.gif

1px.gif

159 ms

logo.png

logo.png

159 ms

loader.svg

loader.svg

158 ms

1px.gif

1px.gif

157 ms

fx-new.jpg

fx-new.jpg

225 ms

fx-promo.jpg

fx-promo.jpg

464 ms

producer01.png

producer01.png

226 ms

producer02.png

producer02.png

225 ms

producer03.png

producer03.png

225 ms

producer04.png

producer04.png

464 ms

producer05.png

producer05.png

463 ms

producer06.png

producer06.png

463 ms

producer07.png

producer07.png

463 ms

producer08.png

producer08.png

581 ms

producer09.png

producer09.png

580 ms

producer10.png

producer10.png

578 ms

logo_background.png

logo_background.png

499 ms

basket.png

basket.png

498 ms

search.png

search.png

499 ms

deco2.png

deco2.png

590 ms

separator.png

separator.png

590 ms

infoicon01.png

infoicon01.png

590 ms

infoicon02.png

infoicon02.png

590 ms

infoicon03.png

infoicon03.png

591 ms

infoicon04.png

infoicon04.png

598 ms

infoicon05.png

infoicon05.png

697 ms

js

js

108 ms

js

js

168 ms

analytics.js

analytics.js

161 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

143 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

261 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

300 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAqnS43lvd8.woff

373 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAr5S43lvd8.woff

374 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RAp5TI3lvd8.woff

376 ms

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvd8.woff

E21x_cfngu7HiRpPX3ZpNE4kY5zKSPmJXkF0VDD2RApATI3lvd8.woff

337 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

577 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

596 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

596 ms

d4g3fpzffq

d4g3fpzffq

302 ms

sm.js

sm.js

952 ms

collect

collect

122 ms

collect

collect

58 ms

clarity.js

clarity.js

39 ms

ga-audiences

ga-audiences

103 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

129 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

109 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

110 ms

Accessibility Review

wiecznepiora.pl accessibility score

72

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

wiecznepiora.pl best practices score

58

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

wiecznepiora.pl SEO score

92

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

wiecznepiora.pl

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