6 sec in total
416 ms
5.3 sec
243 ms
Visit geberit.pl now to see the best up-to-date Geberit content for Poland and also check out these interesting facts you probably never knew about geberit.pl
Witamy w Geberit! Dowiedz się więcej o produktach, kompetencjach, usługach, o nas oraz o możliwościach zrobienia kariery.
Visit geberit.plWe analyzed Geberit.pl page load time and found that the first response time was 416 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
geberit.pl performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value4.9 s
29/100
25%
Value4.3 s
75/100
10%
Value640 ms
47/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
416 ms
362 ms
1217 ms
191 ms
194 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 88% of them (56 requests) were addressed to the original Geberit.pl, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Geberit.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Geberit.pl.
Page size can be reduced by 1.1 MB (58%)
1.9 MB
787.7 kB
In fact, the total size of Geberit.pl main page is 1.9 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.3 kB or 76% of the original size.
Potential reduce by 11.4 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. Geberit images are well optimized though.
Potential reduce by 903.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 903.6 kB or 77% of the original size.
Potential reduce by 142.8 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. Geberit.pl needs all CSS files to be minified and compressed as it can save up to 142.8 kB or 83% of the original size.
Number of requests can be reduced by 39 (66%)
59
20
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geberit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
geberit.pl
416 ms
www.geberit.pl
362 ms
index.html
1217 ms
global.css
191 ms
header.css
194 ms
navigation.css
197 ms
content.css
1298 ms
sidebar.css
1199 ms
font.css
1199 ms
jqueryfancybox-134.css
285 ms
lightwindow.css
288 ms
jqtransform.css
291 ms
interactive_description.css
381 ms
local.css
385 ms
locator.css
387 ms
target_installer.css
492 ms
target_architect.css
1491 ms
target_enduser.css
1490 ms
deeplink.css
587 ms
homepage_country.css
685 ms
jquerymin.js
883 ms
jqueryeasing.js
982 ms
jquery-ui-192custommin.js
1276 ms
jquerytoolsmin.js
1552 ms
jqueryprint.js
1295 ms
cufon.js
1375 ms
Grotesk_Bold_700font.js
1591 ms
Geberit_Light_400font.js
1616 ms
Aktiv_Medium_400font.js
1484 ms
bxSlider.js
1583 ms
fancybox.js
1585 ms
common.js
1685 ms
cHome.js
1583 ms
country_homepage.js
1689 ms
img_bath_1_A1_sigma70_bg_width_1280_height_N.jpg
1439 ms
img_logo_header_geberit_gruppe-de.gif
103 ms
img_schifffahrtsmuseum_width_458_height_226.jpg
1336 ms
img_museum_lyon_width_458_height_226.jpg
1197 ms
img_financial_district_width_458_height_226.jpg
1334 ms
img_boerse_shenzen_width_458_height_226.jpg
1291 ms
1_fotWKryski_Muzeum_Historii_ydw_Polskich_POLIN_-_Copy_width_458_height_226.jpg
290 ms
img_de_rotterdam_width_458_height_226.jpg
1488 ms
img_park_royal_width_458_height_226.jpg
1430 ms
230691_installer_people_width_132_height_125.jpg
1388 ms
img_Monolith_wall-hung_WC_and_washbasin~1_width_132_height_125.jpg
1431 ms
230673_enduser_people_bathroom_width_132_height_125.jpg
1435 ms
gtm.js
96 ms
bg_header_worldmap.png
1472 ms
bg_arrow_homeTeaser.png
1513 ms
icon_print.png
1512 ms
icon_tell_a_friend.png
1513 ms
icon_facebook.png
1515 ms
icon_twitter.png
1564 ms
transgif.png
1487 ms
prev_homeSlider.png
1530 ms
next_homeSlider.png
1529 ms
analytics.js
7 ms
linkid.js
7 ms
host-address.jsp
408 ms
host-address.jsp
103 ms
collect
4 ms
collect
69 ms
ga-audiences
52 ms
print.css
99 ms
geberit.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
Buttons do not have an accessible name
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.
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.
geberit.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
Missing source maps for large first-party JavaScript
geberit.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geberit.pl can be misinterpreted by Google and other search engines. Our service has detected that Polish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Geberit.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.
geberit.pl
Open Graph description is not detected on the main page of Geberit. 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: