Tools & Wizards About Us
ign.com.pl screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ign.com.pl

IGN – Internetowa Giełda Nieruchomości

Page Load Speed

7.8 sec in total

First Response

1.8 sec

Resources Loaded

5.6 sec

Page Rendered

377 ms

ign.com.pl screenshot

About Website

Welcome to ign.com.pl homepage info - get ready to check IGN Com best content right away, or after learning these important things about ign.com.pl

Visit ign.com.pl

Key Findings

We analyzed Ign.com.pl page load time and found that the first response time was 1.8 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

ign.com.pl performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value4,240 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.172

70/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

ign.com.pl

1836 ms

css

36 ms

fontawesome.min.css

229 ms

solid.min.css

344 ms

jquery.fancybox.min.css

362 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 75% of them (100 requests) were addressed to the original Ign.com.pl, 16% (22 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ign.com.pl.

Page Optimization Overview & Recommendations

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

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ign.com.pl main page is 3.2 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. 75% 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 149.0 kB

  • Original 178.1 kB
  • After minification 174.6 kB
  • After compression 29.1 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 149.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 13.0 kB

  • Original 2.4 MB
  • After minification 2.3 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. IGN Com images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 9.2 kB

  • Original 566.1 kB
  • After minification 566.1 kB
  • After compression 556.9 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

-2%

Potential reduce by 1.5 kB

  • Original 80.7 kB
  • After minification 80.7 kB
  • After compression 79.2 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. Ign.com.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 87 (81%)

Requests Now

108

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ign.com.pl

ign.com.pl

1836 ms

css

css

36 ms

fontawesome.min.css

fontawesome.min.css

229 ms

solid.min.css

solid.min.css

344 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

362 ms

slick.css

slick.css

361 ms

flatpickr.min.css

flatpickr.min.css

364 ms

select2.min.css

select2.min.css

370 ms

intlTelInput.min.css

intlTelInput.min.css

367 ms

jquery-ui.min.css

jquery-ui.min.css

460 ms

grid.min.css

grid.min.css

477 ms

common.min.css

common.min.css

476 ms

frontend.min.css

frontend.min.css

478 ms

frontend.min.css

frontend.min.css

483 ms

frontend.min.css

frontend.min.css

484 ms

style.min.css

style.min.css

581 ms

minireset.min.css

minireset.min.css

588 ms

flexboxgrid.min.css

flexboxgrid.min.css

589 ms

frontend.min.css

frontend.min.css

594 ms

style.css

style.css

597 ms

elementor-icons.min.css

elementor-icons.min.css

599 ms

frontend-lite.min.css

frontend-lite.min.css

696 ms

swiper.min.css

swiper.min.css

704 ms

post-6.css

post-6.css

703 ms

frontend-lite.min.css

frontend-lite.min.css

706 ms

uael-frontend.min.css

uael-frontend.min.css

968 ms

global.css

global.css

718 ms

post-1412.css

post-1412.css

810 ms

post-26.css

post-26.css

815 ms

post-36.css

post-36.css

815 ms

css

css

128 ms

fontawesome.min.css

fontawesome.min.css

821 ms

solid.min.css

solid.min.css

832 ms

brands.min.css

brands.min.css

924 ms

jquery.min.js

jquery.min.js

1048 ms

jquery-migrate.min.js

jquery-migrate.min.js

928 ms

script.min.js

script.min.js

839 ms

api.js

api.js

52 ms

js

js

87 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

849 ms

js

js

87 ms

widget-icon-box.min.css

widget-icon-box.min.css

937 ms

widget-icon-list.min.css

widget-icon-list.min.css

819 ms

animations.min.css

animations.min.css

889 ms

core.min.js

core.min.js

870 ms

mouse.min.js

mouse.min.js

870 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

963 ms

jquery.fileupload.js

jquery.fileupload.js

962 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

958 ms

slick.min.js

slick.min.js

867 ms

jquery.sticky-sidebar.min.js

jquery.sticky-sidebar.min.js

852 ms

php-date-formatter.min.js

php-date-formatter.min.js

849 ms

flatpickr.min.js

flatpickr.min.js

940 ms

select2.full.min.js

select2.full.min.js

935 ms

intlTelInput.min.js

intlTelInput.min.js

935 ms

sortable.min.js

sortable.min.js

831 ms

common.min.js

common.min.js

845 ms

slider.min.js

slider.min.js

827 ms

imagesloaded.min.js

imagesloaded.min.js

977 ms

frontend.min.js

frontend.min.js

972 ms

jquery.geocomplete.min.js

jquery.geocomplete.min.js

971 ms

markerclustererplus.min.js

markerclustererplus.min.js

875 ms

oms.min.js

oms.min.js

882 ms

common.min.js

common.min.js

881 ms

frontend.min.js

frontend.min.js

936 ms

pl.js

pl.js

925 ms

pl.js

pl.js

837 ms

focus-visible.min.js

focus-visible.min.js

830 ms

hoverIntent.min.js

hoverIntent.min.js

831 ms

comment-reply.min.js

comment-reply.min.js

838 ms

frontend.min.js

frontend.min.js

924 ms

frontend.min.js

frontend.min.js

834 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

831 ms

jquery-numerator.min.js

jquery-numerator.min.js

824 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

811 ms

webpack.runtime.min.js

webpack.runtime.min.js

755 ms

frontend-modules.min.js

frontend-modules.min.js

833 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

827 ms

recaptcha__en.js

recaptcha__en.js

224 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

648 ms

wp-polyfill.min.js

wp-polyfill.min.js

675 ms

hooks.min.js

hooks.min.js

676 ms

i18n.min.js

i18n.min.js

582 ms

frontend.min.js

frontend.min.js

666 ms

waypoints.min.js

waypoints.min.js

665 ms

frontend.min.js

frontend.min.js

669 ms

elements-handlers.min.js

elements-handlers.min.js

670 ms

jquery.sticky.min.js

jquery.sticky.min.js

656 ms

logo-ign.gif

logo-ign.gif

689 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

98 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

112 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

145 ms

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

pxiByp8kv8JHgFVrLGT9Z1xlEw.woff

165 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

167 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

167 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

166 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

166 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

165 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

165 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

167 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff

167 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff

167 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff

166 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff

167 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff

168 ms

fa-solid-900.woff

fa-solid-900.woff

915 ms

fa-solid-900.woff

fa-solid-900.woff

915 ms

fa-brands-400.woff

fa-brands-400.woff

806 ms

baner-1.jpg

baner-1.jpg

1253 ms

429297_3-400x300.jpeg

429297_3-400x300.jpeg

677 ms

429330_5-400x300.jpeg

429330_5-400x300.jpeg

806 ms

429288_1-400x300.jpeg

429288_1-400x300.jpeg

670 ms

429330_2-400x300.jpeg

429330_2-400x300.jpeg

778 ms

429330_DSC_1062-400x300.jpeg

429330_DSC_1062-400x300.jpeg

877 ms

428978_1-400x300.jpg

428978_1-400x300.jpg

873 ms

onas-1.png

onas-1.png

1086 ms

mieszkania-1.jpg

mieszkania-1.jpg

858 ms

dom-1.jpg

dom-1.jpg

808 ms

dzialka-1.jpg

dzialka-1.jpg

914 ms

lokale-1.jpg

lokale-1.jpg

922 ms

lokale.jpg

lokale.jpg

1261 ms

baner-3.png

baner-3.png

1262 ms

fallback

fallback

39 ms

fallback

fallback

33 ms

fallback

fallback

36 ms

fallback__ltr.css

fallback__ltr.css

6 ms

css

css

24 ms

logo_48.png

logo_48.png

3 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

4 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

5 ms

Accessibility Review

ign.com.pl accessibility score

95

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

Links do not have a discernible name

Best Practices

ign.com.pl best practices score

75

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ign.com.pl SEO score

85

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 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 Ign.com.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 Ign.com.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

ign.com.pl

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