Tools & Wizards About Us
epnos.pl screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

epnos.pl

Nasiona roślin - polski producent | Sklep internetowy PNOS

Page Load Speed

4 sec in total

First Response

751 ms

Resources Loaded

2.9 sec

Page Rendered

358 ms

epnos.pl screenshot

About Website

Click here to check amazing E PNOS content for Poland. Otherwise, check out these important facts you probably never knew about epnos.pl

Nasiona warzyw od polskiego producenta! - sklep internetowy PNOS ✅ 100% Naturalne | Różne odmiany ✅ Konkurencyjne ceny | Profesjonalne doradztwo ✅ Szybka dostawa - Sprawdź już teraz!

Visit epnos.pl

Key Findings

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

Performance Metrics

epnos.pl performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,200 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.332

34/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

pnos.pl

751 ms

MTI6OTI6NS4yNC4xOQ.css

322 ms

fastdom.min.js

417 ms

main.6f1b0801cff7b64dda07.min.js

846 ms

pl_PL.js

418 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Epnos.pl, 9% (2 requests) were made to Googletagmanager.com and 4% (1 request) were made to Dcsaascdn.net. The less responsive or slowest element that took the longest time to load (846 ms) relates to the external source Pnos.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 305.5 kB (16%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-92%

Potential reduce by 279.4 kB

  • Original 304.0 kB
  • After minification 139.9 kB
  • After compression 24.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 164.2 kB, which is 54% 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 279.4 kB or 92% of the original size.

Image Optimization

-2%

Potential reduce by 25.9 kB

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

JavaScript Optimization

-0%

Potential reduce by 191 B

  • Original 242.5 kB
  • After minification 242.5 kB
  • After compression 242.3 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.9 kB
  • After minification 60.9 kB
  • After compression 60.9 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. Epnos.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (33%)

Requests Now

21

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E PNOS. 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 JavaScripts and as a result speed up the page load time.

Network Requests Diagram

pnos.pl

pnos.pl

751 ms

MTI6OTI6NS4yNC4xOQ.css

MTI6OTI6NS4yNC4xOQ.css

322 ms

fastdom.min.js

fastdom.min.js

417 ms

main.6f1b0801cff7b64dda07.min.js

main.6f1b0801cff7b64dda07.min.js

846 ms

pl_PL.js

pl_PL.js

418 ms

user.js

user.js

460 ms

front-api-1.4.0.min.js

front-api-1.4.0.min.js

477 ms

js

js

50 ms

gtm.js

gtm.js

117 ms

fbevents.js

fbevents.js

117 ms

1px.gif

1px.gif

117 ms

logo.png

logo.png

121 ms

loader.svg

loader.svg

117 ms

pl_PL.png

pl_PL.png

119 ms

201709_SLIDER_WWW-2-1.jpg

201709_SLIDER_WWW-2-1.jpg

765 ms

08_polskie_nasiona_pnos_KWIATY.jpg

08_polskie_nasiona_pnos_KWIATY.jpg

534 ms

06_polskie_nasiona_pnos_zio%C3%A9a.jpg

06_polskie_nasiona_pnos_zio%C3%A9a.jpg

766 ms

00a727e0f59f117207a648502ec0a888.jpg

00a727e0f59f117207a648502ec0a888.jpg

637 ms

PNOS%20-%20to%20jest%20to%20na%20czym%20sie%20znamy.JPG

PNOS%20-%20to%20jest%20to%20na%20czym%20sie%20znamy.JPG

317 ms

logo_background.png

logo_background.png

268 ms

basket.png

basket.png

363 ms

ico_mail.png

ico_mail.png

378 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

414 ms

Accessibility Review

epnos.pl accessibility score

66

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

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.

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

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

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

Missing source maps for large first-party JavaScript

SEO Factors

epnos.pl SEO score

91

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

epnos.pl

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