Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

hanget.pl

Kancelaria Nieruchomości HANGET - witamy w naszej kancelarii

Page Load Speed

4.7 sec in total

First Response

333 ms

Resources Loaded

4.1 sec

Page Rendered

255 ms

hanget.pl screenshot

About Website

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

Kancelaria Nieruchomości HANGET jest pierwszym w Cieszynie biurem nieruchomości, zapewniającym swoim Klientom całkowicie kompleksową ...

Visit hanget.pl

Key Findings

We analyzed Hanget.pl page load time and found that the first response time was 333 ms and then it took 4.4 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

hanget.pl performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,460 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

hanget.pl

333 ms

hanget.pl

666 ms

wpfp.css

278 ms

simpleblogcard.css

350 ms

styles.css

350 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 78% of them (88 requests) were addressed to the original Hanget.pl, 17% (19 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hanget.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 525.1 kB (29%)

Content Size

1.8 MB

After Optimization

1.3 MB

In fact, the total size of Hanget.pl main page is 1.8 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. 65% of websites need less resources to load. Images take 689.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 231.3 kB

  • Original 266.2 kB
  • After minification 242.3 kB
  • After compression 34.9 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 231.3 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 25.4 kB

  • Original 689.1 kB
  • After minification 663.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. HANGET images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 222.6 kB

  • Original 667.6 kB
  • After minification 667.6 kB
  • After compression 445.1 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 222.6 kB or 33% of the original size.

CSS Optimization

-25%

Potential reduce by 45.8 kB

  • Original 184.1 kB
  • After minification 183.0 kB
  • After compression 138.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. Hanget.pl needs all CSS files to be minified and compressed as it can save up to 45.8 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 80 (90%)

Requests Now

89

After Optimization

9

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

Accessibility Review

hanget.pl accessibility score

68

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.

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

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

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hanget.pl SEO score

99

Search Engine Optimization Advices

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