Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

progenis.pl

Progenis - Bank Komórek Macierzystych krwi pępowinowej - Progenis

Page Load Speed

3.6 sec in total

First Response

293 ms

Resources Loaded

2.9 sec

Page Rendered

379 ms

About Website

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

Krew pępowinowa i zawarte w niej komórki macierzyste mogą w przyszłości uratować zdrowie Twojego dziecka. Zabezpiecz je w trakcie porodu.

Visit progenis.pl

Key Findings

We analyzed Progenis.pl page load time and found that the first response time was 293 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

progenis.pl performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

progenis.pl

293 ms

www.progenis.pl

854 ms

style.min.css

189 ms

dashicons.min.css

381 ms

everest-forms.css

292 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 80% of them (41 requests) were addressed to the original Progenis.pl, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (854 ms) belongs to the original domain Progenis.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.4 kB (8%)

Content Size

1.3 MB

After Optimization

1.2 MB

In fact, the total size of Progenis.pl main page is 1.3 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 983.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 68.6 kB

  • Original 86.3 kB
  • After minification 84.7 kB
  • After compression 17.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 68.6 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 24.6 kB

  • Original 983.2 kB
  • After minification 958.6 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. Progenis images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 988 B

  • Original 153.2 kB
  • After minification 153.2 kB
  • After compression 152.2 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

-5%

Potential reduce by 4.2 kB

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

Requests Breakdown

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

Requests Now

47

After Optimization

18

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

Accessibility Review

progenis.pl accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

progenis.pl best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

progenis.pl SEO score

92

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

Image elements do not have [alt] attributes

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 Progenis.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 Progenis.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 data is detected on the main page of Progenis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: