9.8 sec in total
724 ms
8.7 sec
342 ms
Welcome to funero.pl homepage info - get ready to check Funero best content right away, or after learning these important things about funero.pl
Od kilkunastu lat dostarczamy trumny do pochówku, kremacyjne i urny. Hurtownia funeralna oferuje również szeroki wybór wyposażenia trumien – zapraszamy.
Visit funero.plWe analyzed Funero.pl page load time and found that the first response time was 724 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
funero.pl performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value6.4 s
10/100
25%
Value17.7 s
0/100
10%
Value10,890 ms
0/100
30%
Value0.113
86/100
15%
Value19.6 s
2/100
10%
724 ms
399 ms
250 ms
251 ms
250 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that all of those requests were addressed to Funero.pl and no external sources were called. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Funero.pl.
Page size can be reduced by 674.2 kB (9%)
7.5 MB
6.8 MB
In fact, the total size of Funero.pl main page is 7.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. 20% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.
Potential reduce by 14.9 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 14.9 kB or 77% of the original size.
Potential reduce by 449.8 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. Funero images are well optimized though.
Potential reduce by 174.2 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 174.2 kB or 65% of the original size.
Potential reduce by 35.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. Funero.pl needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 84% 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 Funero. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
funero.pl
724 ms
style.css
399 ms
style.css
250 ms
style.css
251 ms
style.css
250 ms
style.css
282 ms
colorbox.min.css
250 ms
jquery.js
722 ms
jquery-migrate.min.js
599 ms
flexy-menu.css
872 ms
jquery-1.10.1.min.js
997 ms
flexy-menu.js
597 ms
jquery.cycle2.min.js
715 ms
jquery.cycle2.carousel.min.js
828 ms
jquery.cycle2.swipe.min.js
829 ms
jquery.cycle2.tile.min.js
953 ms
jquery.cycle2.video.min.js
954 ms
script.js
1265 ms
script.js
1061 ms
client.js
1100 ms
jquery.colorbox.1.5.9-min.js
1193 ms
wp-emoji-release.min.js
788 ms
tlo-new.jpg
2060 ms
t.png
334 ms
men2.png
1958 ms
polska.png
447 ms
rosja.png
447 ms
en.png
488 ms
funero-trumny-urny-galanteria-pogrzebowa.png
1355 ms
s1.png
1405 ms
s2.png
1433 ms
TD1-TD1c.png
1577 ms
TD2-TD2c.png
2412 ms
TD3-TD3c.png
2433 ms
TD4-TD4c.png
2456 ms
TD5-TD5c.png
2604 ms
TD6-TD6c.png
3073 ms
TS1-TS1c.png
3166 ms
TS2-TS2c.png
3384 ms
TS4-TS4c.png
3521 ms
TS5-TS6c.png
3534 ms
sprite-arrows.png
6330 ms
katalog.png
7007 ms
polska-firma.jpg
6444 ms
facebook.png
3753 ms
twitter.png
6488 ms
funero.pl accessibility score
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
funero.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
funero.pl SEO score
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 Funero.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 Funero.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.
funero.pl
Open Graph description is not detected on the main page of Funero. 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: