Tools & Wizards About Us
historyfan.pl screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

historyfan.pl

Centrum Fanów Informacji - Zawsze jesteś poinformowany

Page Load Speed

11.1 sec in total

First Response

647 ms

Resources Loaded

8.4 sec

Page Rendered

2 sec

historyfan.pl screenshot

About Website

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

Bądź zawsze poinformowany. Czytaj nasze teksty i dowiedz się dużo ciekawych rzeczy z różnych dziedzin. Wszystko czego potrzebujesz jest w jednym miejscu.

Visit historyfan.pl

Key Findings

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

Performance Metrics

historyfan.pl performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

historyfan.pl

647 ms

wp-emoji-release.min.js

341 ms

trx_addons_icons.css

458 ms

oys6eoo.css

277 ms

fontello.css

472 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 96% of them (76 requests) were addressed to the original Historyfan.pl, 1% (1 request) were made to Use.typekit.net and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Historyfan.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.1 kB (13%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 136.5 kB

  • Original 158.1 kB
  • After minification 152.9 kB
  • After compression 21.6 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 136.5 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 4.8 kB

  • Original 689.4 kB
  • After minification 684.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. Historyfan images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 4.0 kB

  • Original 144.6 kB
  • After minification 144.6 kB
  • After compression 140.6 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

-7%

Potential reduce by 17.8 kB

  • Original 271.8 kB
  • After minification 271.8 kB
  • After compression 254.0 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. Historyfan.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (85%)

Requests Now

75

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historyfan.pl

historyfan.pl

647 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

341 ms

trx_addons_icons.css

trx_addons_icons.css

458 ms

oys6eoo.css

oys6eoo.css

277 ms

fontello.css

fontello.css

472 ms

powerkit.css

powerkit.css

488 ms

style.min.css

style.min.css

491 ms

advanced-popups-public.css

advanced-popups-public.css

491 ms

styles.css

styles.css

573 ms

public-powerkit-author-box.css

public-powerkit-author-box.css

562 ms

public-powerkit-social-links.css

public-powerkit-social-links.css

596 ms

public-powerkit-twitter.css

public-powerkit-twitter.css

595 ms

magnific-popup.min.css

magnific-popup.min.css

601 ms

style.css

style.css

609 ms

custom.css

custom.css

685 ms

stylesheet.css

stylesheet.css

686 ms

elementor-icons.min.css

elementor-icons.min.css

715 ms

custom-frontend-legacy.min.css

custom-frontend-legacy.min.css

716 ms

custom-frontend.min.css

custom-frontend.min.css

778 ms

post-9016.css

post-9016.css

738 ms

post-14697.css

post-14697.css

805 ms

__styles-full.css

__styles-full.css

1001 ms

trx_addons.animations.css

trx_addons.animations.css

857 ms

style.css

style.css

839 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

862 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

903 ms

style.css

style.css

1137 ms

__plugins-full.css

__plugins-full.css

1048 ms

powerkit.css

powerkit.css

987 ms

extra-style.css

extra-style.css

985 ms

__custom.css

__custom.css

1032 ms

css

css

39 ms

jquery.min.js

jquery.min.js

1243 ms

jquery-migrate.min.js

jquery-migrate.min.js

1112 ms

post-13518.css

post-13518.css

1121 ms

post-1063.css

post-1063.css

1172 ms

animations.min.css

animations.min.css

1173 ms

advanced-popups-public.js

advanced-popups-public.js

1338 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1308 ms

p.css

p.css

26 ms

wp-polyfill.min.js

wp-polyfill.min.js

1055 ms

index.js

index.js

977 ms

magnific.js

magnific.js

923 ms

jquery.cookie.js

jquery.cookie.js

945 ms

trx_popup.script.js

trx_popup.script.js

980 ms

__scripts-full.js

__scripts-full.js

1121 ms

superfish.min.js

superfish.min.js

911 ms

tweenmax.min.js

tweenmax.min.js

1114 ms

__scripts-full.js

__scripts-full.js

997 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1048 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

977 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

985 ms

skin.js

skin.js

1024 ms

core.min.js

core.min.js

1035 ms

tabs.min.js

tabs.min.js

1000 ms

effect.min.js

effect.min.js

1010 ms

effect-fade.min.js

effect-fade.min.js

1030 ms

webpack.runtime.min.js

webpack.runtime.min.js

1014 ms

frontend-modules.min.js

frontend-modules.min.js

1026 ms

waypoints.min.js

waypoints.min.js

1003 ms

swiper.min.js

swiper.min.js

1042 ms

share-link.min.js

share-link.min.js

987 ms

dialog.min.js

dialog.min.js

990 ms

frontend.min.js

frontend.min.js

945 ms

preloaded-modules.min.js

preloaded-modules.min.js

979 ms

CFI.png

CFI.png

693 ms

logo1401.png

logo1401.png

693 ms

dom-3.jpg

dom-3.jpg

2103 ms

podnoszenia-img-367-642x427.jpg

podnoszenia-img-367-642x427.jpg

830 ms

zobacz-img-57-642x427.jpg

zobacz-img-57-642x427.jpg

831 ms

placeholder.png

placeholder.png

831 ms

placeholder.png

placeholder.png

832 ms

oswietlenie-rowerowe-25-120x120.jpeg

oswietlenie-rowerowe-25-120x120.jpeg

832 ms

cropped-user4-56x56.jpg

cropped-user4-56x56.jpg

802 ms

fontello.woff

fontello.woff

1157 ms

trx_addons_icons.woff

trx_addons_icons.woff

1076 ms

powerkit-icons.woff

powerkit-icons.woff

141 ms

__responsive-full.css

__responsive-full.css

130 ms

__responsive-full.css

__responsive-full.css

147 ms

Accessibility Review

historyfan.pl accessibility score

79

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-hidden="true"] elements contain focusable descendents

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

historyfan.pl SEO score

91

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

historyfan.pl

Open Graph data is detected on the main page of Historyfan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: