Tools & Wizards About Us
romer.pl screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

romer.pl

Tomasz Romer - Prywatny gabinet endokrynologiczny

Page Load Speed

1.8 sec in total

First Response

210 ms

Resources Loaded

1.5 sec

Page Rendered

99 ms

romer.pl screenshot

About Website

Click here to check amazing Romer content. Otherwise, check out these important facts you probably never knew about romer.pl

Profesor Tomasz Romer - Endokrynolog - Gabinet prywatny - Warszawa

Visit romer.pl

Key Findings

We analyzed Romer.pl page load time and found that the first response time was 210 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

romer.pl performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

54/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

romer.pl

210 ms

www.romer.pl

468 ms

style.css

99 ms

1.gif

208 ms

p.gif

276 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that all of those requests were addressed to Romer.pl and no external sources were called. The less responsive or slowest element that took the longest time to load (792 ms) belongs to the original domain Romer.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.5 kB (21%)

Content Size

283.9 kB

After Optimization

225.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Romer.pl main page is 283.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 5% of websites need less resources to load. Images take 280.4 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 2.1 kB

  • Original 3.3 kB
  • After minification 3.2 kB
  • After compression 1.2 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 2.1 kB or 63% of the original size.

Image Optimization

-20%

Potential reduce by 56.4 kB

  • Original 280.4 kB
  • After minification 224.1 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. Obviously, Romer needs image optimization as it can save up to 56.4 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-19%

Potential reduce by 45 B

  • Original 241 B
  • After minification 241 B
  • After compression 196 B

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. Romer.pl needs all CSS files to be minified and compressed as it can save up to 45 B or 19% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • CSS

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Romer. According to our analytics all requests are already optimized.

Network Requests Diagram

romer.pl

romer.pl

210 ms

www.romer.pl

www.romer.pl

468 ms

style.css

style.css

99 ms

1.gif

1.gif

208 ms

p.gif

p.gif

276 ms

20200715_173900.png

20200715_173900.png

792 ms

T.Romer%202008-02-10.jpg

T.Romer%202008-02-10.jpg

418 ms

cl.gif

cl.gif

183 ms

tlo.gif

tlo.gif

184 ms

cp.gif

cp.gif

200 ms

Accessibility Review

romer.pl accessibility score

76

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

Image elements do not have [alt] attributes

Best Practices

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

SEO Factors

romer.pl SEO score

67

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

Language and Encoding

  • Language Detected

    PL

  • Language Claimed

    PL

  • Encoding

    ISO8859-2

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Romer.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 Romer.pl main page’s claimed encoding is iso8859-2. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

romer.pl

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