7.2 sec in total
1.1 sec
5.3 sec
735 ms
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.plWe analyzed Fru.pl page load time and found that the first response time was 1.1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fru.pl performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value6.5 s
8/100
25%
Value11.6 s
4/100
10%
Value3,680 ms
1/100
30%
Value0.152
75/100
15%
Value19.7 s
2/100
10%
1111 ms
1584 ms
56 ms
881 ms
1985 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 53% of them (27 requests) were addressed to the original Fru.pl, 8% (4 requests) were made to Google-analytics.com and 8% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fru.pl.
Page size can be reduced by 2.7 MB (73%)
3.8 MB
1.0 MB
In fact, the total size of Fru.pl main page is 3.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. 40% of websites need less resources to load. Javascripts take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 271.8 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 271.8 kB or 81% of the original size.
Potential reduce by 88.3 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. Obviously, FRU needs image optimization as it can save up to 88.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.8 MB
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 1.8 MB or 78% of the original size.
Potential reduce by 538.4 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 needs all CSS files to be minified and compressed as it can save up to 538.4 kB or 82% of the original size.
Number of requests can be reduced by 19 (42%)
45
26
The browser has sent 45 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 10 to 1 for JavaScripts and as a result speed up the page load time.
www.fru.pl
1111 ms
all.min.css
1584 ms
css
56 ms
vendor.js
881 ms
templates.min.js
1985 ms
application.min.js
1733 ms
pl.js
467 ms
gtm.js
280 ms
logo-inverse.png
277 ms
opinia1.png
277 ms
opinia2.png
405 ms
opinia3.png
279 ms
chrome.png
320 ms
firefox.png
357 ms
ie8.png
516 ms
opera.png
404 ms
safari.png
478 ms
PL.png
498 ms
uploaded.photos.destinations.gb.lon.offer-medium
1468 ms
uploaded.photos.destinations.fr.par.offer-medium
440 ms
uploaded.photos.destinations.pl.gdn.offer-medium
498 ms
uploaded.photos.destinations.it.rom.offer-medium
1467 ms
uploaded.photos.destinations.pl.wro.offer-medium
541 ms
uploaded.photos.destinations.es.bcn.offer-medium
1414 ms
prefooter-sprite1.png
1466 ms
payments.png
1414 ms
VolaFruModern.ttf
1414 ms
conversion_async.js
46 ms
analytics.js
62 ms
66 ms
78 ms
collect
17 ms
collect
59 ms
39 ms
37 ms
ga-audiences
22 ms
sdk.js
796 ms
collect
154 ms
collect
154 ms
sm.js
219 ms
ga-audiences
21 ms
73 ms
xd_arbiter.php
66 ms
r.gif
777 ms
rv.gif
121 ms
collect
15 ms
fbevents.js
9 ms
3 ms
like.php
78 ms
xd_arbiter.php
17 ms
LVx-xkvaJ0b.png
39 ms
fru.pl accessibility score
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
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fru.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
fru.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
PL
PL
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.
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: