Tools & Wizards About Us
fru.pl screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

fru.pl

FRU.PL - Bilety Lotnicze - Tanie Loty

Page Load Speed

3.7 sec in total

First Response

37 ms

Resources Loaded

3.6 sec

Page Rendered

104 ms

fru.pl screenshot

About Website

Welcome to fru.pl homepage info - get ready to check FRU best content for Poland right away, or after learning these important things about fru.pl

Tanie loty, bilety lotnicze i tanie linie lotnicze w jednym miejscu. Dobra oferta połączeń lotniczych, rezerwacja hoteli i wynajem samochodów. Sprawdź ofertę FRU.PL teraz.

Visit fru.pl

Key Findings

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

Performance Metrics

fru.pl performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value5,050 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

fru.pl

37 ms

www.fru.pl

1085 ms

ith-stencil-components.css

34 ms

ith-stencil-components.js

62 ms

home.min.css

43 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 82% of them (32 requests) were addressed to the original Fru.pl, 3% (1 request) were made to Fonts.googleapis.com and 3% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Fru.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 288.6 kB (9%)

Content Size

3.4 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 279.1 kB

  • Original 366.5 kB
  • After minification 366.2 kB
  • After compression 87.3 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 279.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-1%

Potential reduce by 9.5 kB

  • Original 720.9 kB
  • After minification 720.9 kB
  • After compression 711.4 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

-0%

Potential reduce by 12 B

  • Original 80.0 kB
  • After minification 80.0 kB
  • After compression 80.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. Fru.pl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (38%)

Requests Now

32

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fru.pl

fru.pl

37 ms

www.fru.pl

www.fru.pl

1085 ms

ith-stencil-components.css

ith-stencil-components.css

34 ms

ith-stencil-components.js

ith-stencil-components.js

62 ms

home.min.css

home.min.css

43 ms

css

css

33 ms

pure.min.js

pure.min.js

69 ms

gtm.js

gtm.js

110 ms

logo-inverse.svg

logo-inverse.svg

142 ms

Hero_HP_mobile_pl.png

Hero_HP_mobile_pl.png

146 ms

mil01.jpg

mil01.jpg

145 ms

vce02.jpg

vce02.jpg

145 ms

rom03.jpg

rom03.jpg

242 ms

blq01.jpg

blq01.jpg

243 ms

vce01.jpg

vce01.jpg

244 ms

Fare_lock_mobile_pl.png

Fare_lock_mobile_pl.png

245 ms

Fare_lock_desktop_pl.png

Fare_lock_desktop_pl.png

245 ms

summer_trends_hp_mobile.png

summer_trends_hp_mobile.png

248 ms

summer_trends_ho_desktop.png

summer_trends_ho_desktop.png

333 ms

facebook-logo.svg

facebook-logo.svg

255 ms

youtube-logo.svg

youtube-logo.svg

253 ms

vendor.min.js

vendor.min.js

291 ms

templates.min.js

templates.min.js

325 ms

application.min.js

application.min.js

362 ms

pl.min.js

pl.min.js

335 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

251 ms

chrome.png

chrome.png

1754 ms

firefox.png

firefox.png

1726 ms

ie8.png

ie8.png

1784 ms

opera.png

opera.png

1739 ms

safari.png

safari.png

1824 ms

sha256.min.js

sha256.min.js

251 ms

uc.js

uc.js

244 ms

js

js

882 ms

fbevents.js

fbevents.js

138 ms

font

font

94 ms

VolaFruModern.ttf

VolaFruModern.ttf

916 ms

shelf-cache.worker.js

shelf-cache.worker.js

689 ms

iataDictionary

iataDictionary

519 ms

Accessibility Review

fru.pl accessibility score

66

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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.

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fru.pl SEO score

80

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

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

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

fru.pl

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