Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

pgn.otodom.pl

Biuro nieruchomości Gryfice - PGN NIERUCHOMOŚCI BIURA GRYFICE KAMIEŃ POMORSKI OBORNIKI | Otodom

Page Load Speed

5.7 sec in total

First Response

990 ms

Resources Loaded

3.4 sec

Page Rendered

1.3 sec

pgn.otodom.pl screenshot

About Website

Visit pgn.otodom.pl now to see the best up-to-date PGN Otodom content for Poland and also check out these interesting facts you probably never knew about pgn.otodom.pl

W Otodom znajdziesz wszystkie oferty i dane kontaktowe biura nieruchomości PGN NIERUCHOMOŚCI BIURA GRYFICE KAMIEŃ POMORSKI OBORNIKI działającego w Gryfice.

Visit pgn.otodom.pl

Key Findings

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

Performance Metrics

pgn.otodom.pl performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

pgn.otodom.pl

990 ms

sw02c81b629ddb46c726e5950a0ba33a40.css

890 ms

sw7f590badb495857683079dde6c26a1dd.js

1113 ms

sw1b0c28b8ebfc34cb54ca6052cfb5520a.js

534 ms

2093450101.js

91 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pgn.otodom.pl, 17% (11 requests) were made to Img40.otodom.pl and 12% (8 requests) were made to Img41.otodom.pl. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Img40.otodom.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.1 kB (77%)

Content Size

582.3 kB

After Optimization

135.2 kB

In fact, the total size of Pgn.otodom.pl main page is 582.3 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. 55% of websites need less resources to load. CSS take 380.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.2 kB

  • Original 71.0 kB
  • After minification 59.0 kB
  • After compression 14.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 12.0 kB, which is 17% 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 56.2 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 47 B

  • Original 5.6 kB
  • After minification 5.5 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. PGN Otodom images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 77.3 kB

  • Original 125.2 kB
  • After minification 123.9 kB
  • After compression 48.0 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 77.3 kB or 62% of the original size.

CSS Optimization

-82%

Potential reduce by 313.6 kB

  • Original 380.5 kB
  • After minification 374.0 kB
  • After compression 66.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. Pgn.otodom.pl needs all CSS files to be minified and compressed as it can save up to 313.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (22%)

Requests Now

59

After Optimization

46

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

Accessibility Review

pgn.otodom.pl accessibility score

57

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Form elements do not have associated labels

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

pgn.otodom.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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pgn.otodom.pl SEO score

81

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 doesn't use 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 Pgn.otodom.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 Pgn.otodom.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 description is not detected on the main page of PGN Otodom. 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: