Tools & Wizards About Us

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

trader.pl

Ogłoszenia Nieruchomości: Mieszkania, Domy - Sprzedaż i Wynajem - Domiporta.pl

Page Load Speed

9 sec in total

First Response

240 ms

Resources Loaded

6.5 sec

Page Rendered

2.3 sec

About Website

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

Szukasz ogłoszeń nieruchomości? W Domiporta.pl znajdziesz 159385 aktualnych ofert sprzedaży i wynajmu w kategoriach: mieszkania, domy, działki, pokoje, garaże i lokale użytkowe. Z nami znajdziesz dom,...

Visit trader.pl

Key Findings

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

Performance Metrics

trader.pl performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value7,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

trader.pl

240 ms

www.domiporta.pl

639 ms

default.min.css

116 ms

default.min.js

235 ms

home.min.css

447 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Trader.pl, 51% (65 requests) were made to Galeria.domiporta.pl and 35% (45 requests) were made to Domiporta.pl. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Galeria.domiporta.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 464.4 kB (5%)

Content Size

10.3 MB

After Optimization

9.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Trader.pl main page is 10.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 9.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 257.8 kB

  • Original 287.0 kB
  • After minification 247.5 kB
  • After compression 29.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. This page needs HTML code to be minified as it can gain 39.5 kB, which is 14% 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 257.8 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 206.4 kB

  • Original 9.7 MB
  • After minification 9.5 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. Trader images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 194 B

  • Original 236.5 kB
  • After minification 236.4 kB
  • After compression 236.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.

Requests Breakdown

Number of requests can be reduced by 28 (23%)

Requests Now

121

After Optimization

93

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

trader.pl accessibility score

60

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

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 IDs are not unique

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

trader.pl best practices score

75

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

Page has valid source maps

SEO Factors

trader.pl SEO score

93

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

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