Tools & Wizards About Us
fort24.pl screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fort24.pl

Self storage Fort24.pl - Przechowywanie rzeczy, Magazyn Warszawa

Page Load Speed

7.5 sec in total

First Response

273 ms

Resources Loaded

6.6 sec

Page Rendered

566 ms

fort24.pl screenshot

About Website

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

Przechowalnia rzeczy w Warszawie. Nowy magazyn samoobsługowy typu self storage zlokalizowany jest w dogodnej lokalizacji w dzielnicy Wola w odległości 3 km od ścisłego centrum Warszawy. Magazyn jest s...

Visit fort24.pl

Key Findings

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

fort24.pl performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value18.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

fort24.pl

273 ms

929 ms

js

88 ms

wp-emoji-release.min.js

235 ms

owl.carousel.css

353 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 70% of them (60 requests) were addressed to the original Fort24.pl, 7% (6 requests) were made to Cookiealert.sruu.pl and 6% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Fort24.pl.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fort24.pl main page is 2.5 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 51.3 kB

  • Original 66.7 kB
  • After minification 65.5 kB
  • After compression 15.4 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 51.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 29.5 kB

  • Original 2.1 MB
  • After minification 2.1 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. Fort24 images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 15.3 kB

  • Original 196.0 kB
  • After minification 195.7 kB
  • After compression 180.7 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

-25%

Potential reduce by 38.6 kB

  • Original 152.9 kB
  • After minification 152.7 kB
  • After compression 114.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. Fort24.pl needs all CSS files to be minified and compressed as it can save up to 38.6 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (77%)

Requests Now

73

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fort24.pl

fort24.pl

273 ms

929 ms

js

js

88 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

235 ms

owl.carousel.css

owl.carousel.css

353 ms

owl.theme.css

owl.theme.css

366 ms

style.min.css

style.min.css

366 ms

styles.css

styles.css

371 ms

animate.css

animate.css

372 ms

font-awesome.min.css

font-awesome.min.css

385 ms

font-awesome.css

font-awesome.css

481 ms

plugin_shortcodes.css

plugin_shortcodes.css

606 ms

storeup-paypal-style.css

storeup-paypal-style.css

478 ms

style.css

style.css

496 ms

aicon_.css

aicon_.css

496 ms

animation.css

animation.css

508 ms

pe-icon-7-stroke.css

pe-icon-7-stroke.css

603 ms

storeup-style.css

storeup-style.css

618 ms

responsive.css

responsive.css

619 ms

css

css

38 ms

js_composer.min.css

js_composer.min.css

820 ms

frontend-gtag.min.js

frontend-gtag.min.js

636 ms

jquery.min.js

jquery.min.js

804 ms

jquery-migrate.min.js

jquery-migrate.min.js

723 ms

js

js

100 ms

frontend_map.js

frontend_map.js

726 ms

js

js

70 ms

CookieAlert-latest.min.js

CookieAlert-latest.min.js

392 ms

css

css

28 ms

prettyPhoto.min.css

prettyPhoto.min.css

663 ms

scripts.js

scripts.js

692 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

773 ms

jquery.sticky.js

jquery.sticky.js

776 ms

sc_script.js

sc_script.js

796 ms

waypoints.min.js

waypoints.min.js

822 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

858 ms

storeup_vc_script.js

storeup_vc_script.js

867 ms

hoverIntent.js

hoverIntent.js

890 ms

superfish.js

superfish.js

897 ms

jquery.fitvids.js

jquery.fitvids.js

916 ms

storeup-custom.js

storeup-custom.js

949 ms

comment-reply.min.js

comment-reply.min.js

973 ms

storeup-post-like.js

storeup-post-like.js

988 ms

api.js

api.js

59 ms

js

js

63 ms

analytics.js

analytics.js

18 ms

storeup-front-script.js

storeup-front-script.js

984 ms

collect

collect

19 ms

collect

collect

84 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

871 ms

ga-audiences

ga-audiences

16 ms

wp-embed.min.js

wp-embed.min.js

764 ms

js_composer_front.min.js

js_composer_front.min.js

799 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

809 ms

CookieAlert-latest.min.js

CookieAlert-latest.min.js

497 ms

style.css

style.css

723 ms

434 ms

logo.png

logo.png

195 ms

about-1.jpg

about-1.jpg

538 ms

storage-form-min.png

storage-form-min.png

2909 ms

1-min.jpg

1-min.jpg

432 ms

2-min.jpg

2-min.jpg

431 ms

3-min.jpg

3-min.jpg

500 ms

4-min.jpg

4-min.jpg

581 ms

5-min.jpg

5-min.jpg

612 ms

6-min.jpg

6-min.jpg

652 ms

js

js

70 ms

grid.svg

grid.svg

617 ms

storage-bg-partial.jpg

storage-bg-partial.jpg

2147 ms

js

js

94 ms

collect

collect

52 ms

fancy_heading_hr.png

fancy_heading_hr.png

521 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

84 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

266 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

269 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

269 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

269 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

717 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

741 ms

Pe-icon-7-stroke.woff

Pe-icon-7-stroke.woff

697 ms

slider-en-min.jpg

slider-en-min.jpg

702 ms

ajax-loader.gif

ajax-loader.gif

363 ms

info.png

info.png

119 ms

close.png

close.png

229 ms

info.png

info.png

116 ms

close.png

close.png

117 ms

Accessibility Review

fort24.pl accessibility score

77

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

fort24.pl best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fort24.pl SEO score

83

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

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fort24.pl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fort24.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

fort24.pl

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