9.7 sec in total
314 ms
9.1 sec
323 ms
Welcome to obi.pl homepage info - get ready to check OBI best content for Poland right away, or after learning these important things about obi.pl
Sprawdź najwyższej jakości materiały do budowy domu i wykończenia wnętrz. Nasza oferta pozwoli Ci tanio i solidnie urządzić dom i ogród.
Visit obi.plWe analyzed Obi.pl page load time and found that the first response time was 314 ms and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
obi.pl performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value8.0 s
2/100
25%
Value6.1 s
44/100
10%
Value910 ms
31/100
30%
Value0.773
5/100
15%
Value13.7 s
11/100
10%
314 ms
455 ms
410 ms
809 ms
628 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 83% of them (55 requests) were addressed to the original Obi.pl, 3% (2 requests) were made to 868680151.log.optimizely.com and 3% (2 requests) were made to A.trkme.net. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Obi.pl.
Page size can be reduced by 1.1 MB (40%)
2.9 MB
1.7 MB
In fact, the total size of Obi.pl main page is 2.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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 120.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 120.3 kB or 83% of the original size.
Potential reduce by 29.6 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. OBI images are well optimized though.
Potential reduce by 386.9 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 386.9 kB or 68% of the original size.
Potential reduce by 599.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. Obi.pl needs all CSS files to be minified and compressed as it can save up to 599.0 kB or 86% of the original size.
Number of requests can be reduced by 26 (43%)
60
34
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OBI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
obi.pl
314 ms
www.obi.pl
455 ms
www.obi.pl
410 ms
home.html
809 ms
obi-generic-styles.css
628 ms
obi-fonts-ceop.css
317 ms
obi-styles.css
727 ms
obi-modules.css
767 ms
obi-media-fixes.css
426 ms
868680151.js
30 ms
modernizr-custom.js
540 ms
webtrekk_v3.js
705 ms
pl_PL.js
1211 ms
stop-hidden-images.js
1795 ms
require.js
1882 ms
ld.js
77 ms
conversion.js
76 ms
geo2.js
1102 ms
event
888 ms
obi-small.png
660 ms
icons-sprite.png
1098 ms
obi-logo-schatten.png
870 ms
obi-logo.png
1000 ms
sticker-market.png
1096 ms
ajax-loader-transparent.gif
1049 ms
market-change.png
1185 ms
obi-print.jpg
1288 ms
slide_1.jpg
1865 ms
slide_mobile.jpg
1811 ms
slide_2.jpg
1950 ms
slide_mobile.jpg
2081 ms
slide_3.jpg
1979 ms
slide_3_mobile.jpg
2011 ms
stage-right.jpg
2426 ms
stage-right-mobile.jpg
2692 ms
stoerer-top-preis.png
2289 ms
43t.gif
2365 ms
star-active.png
2407 ms
star-active-inactive.png
2495 ms
star-inactive.png
2552 ms
t12.jpg
3153 ms
teaser_t6_left.jpg
3009 ms
teaser_t6_right.jpg
3078 ms
270x445-orange.jpg
2769 ms
bottom-zamow.jpg
3311 ms
teaser_1.png
3833 ms
teaser_1_mobil.jpg
3595 ms
teaser_1.jpg
3388 ms
S12_Metamorfozy.jpg
4164 ms
ico-obi.png
3569 ms
obi-logo-footer.png
3697 ms
obisans_ce_bold-webfont.woff
3601 ms
event
136 ms
blind.gif
3352 ms
645 ms
648 ms
ifo.js
3899 ms
273 ms
97 ms
obi-print.css
236 ms
wt
829 ms
stage2.js
299 ms
jcarousel.js
397 ms
specials.js
496 ms
jquery-dotdotdot.js
120 ms
btn_stage_disabled.png
321 ms
obi.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
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.
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.
obi.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
obi.pl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Obi.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 Obi.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.
obi.pl
Open Graph description is not detected on the main page of OBI. 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: