8.5 sec in total
459 ms
7.8 sec
247 ms
Click here to check amazing OBO content for Iran. Otherwise, check out these important facts you probably never knew about obo.de
OBO Bettermann ist einer der führenden Hersteller von Installationssystemen für die elektrotechnische Ausstattung von Gebäuden und Anlagen.
Visit obo.deWe analyzed Obo.de page load time and found that the first response time was 459 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
obo.de performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value10.2 s
0/100
25%
Value7.7 s
25/100
10%
Value1,350 ms
17/100
30%
Value0.069
96/100
15%
Value11.2 s
20/100
10%
459 ms
278 ms
176 ms
368 ms
360 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 87% of them (66 requests) were addressed to the original Obo.de, 7% (5 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Obo.de.
Page size can be reduced by 859.6 kB (40%)
2.2 MB
1.3 MB
In fact, the total size of Obo.de main page is 2.2 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.3 MB which makes up the majority of the site volume.
Potential reduce by 44.2 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. This page needs HTML code to be minified as it can gain 15.8 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 44.2 kB or 84% of the original size.
Potential reduce by 251.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. Obviously, OBO needs image optimization as it can save up to 251.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 453.5 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 453.5 kB or 68% of the original size.
Potential reduce by 110.5 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. Obo.de needs all CSS files to be minified and compressed as it can save up to 110.5 kB or 86% of the original size.
Number of requests can be reduced by 21 (29%)
72
51
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OBO. 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 6 to 1 for CSS and as a result speed up the page load time.
obo.de
459 ms
de-de
278 ms
normalize.css
176 ms
main.css
368 ms
spotlight.css
360 ms
cart.css
367 ms
jquery.fancybox.css
358 ms
obo.css
360 ms
modernizr-2.6.2.min.js
365 ms
js
80 ms
jquery-1.10.2.min.js
891 ms
plugins.js
902 ms
jquery.fancybox.pack.js
533 ms
flowplayer.min.js
719 ms
jquery.cookie.js
1063 ms
main.js
536 ms
spotlight.js
708 ms
search.js
712 ms
cart.js
879 ms
bg_texture.jpg
852 ms
gtm.js
66 ms
bg_header.png
206 ms
icon-sprites.png
709 ms
navi_layer_vbs.jpg
206 ms
navi-layer-tbs.png
398 ms
navi-layer-kts.png
1503 ms
navi-layer-bss.png
576 ms
navi-layer-lfs.png
403 ms
navi-layer-egs.png
593 ms
navi-layer-ufs.png
763 ms
navi-layer-energie.jpg
598 ms
navi-layer-industrie.jpg
756 ms
navi-layer-mobilitaet.jpg
778 ms
navi-layer-dienstleistung.jpg
936 ms
navi-layer-2.jpg
1252 ms
navi-layer-1.jpg
1120 ms
navi-layer-bet.jpg
1872 ms
navi-layer-job.jpg
1527 ms
navi-layer-leiferant.jpg
1306 ms
Nachhaltigkeit_navi-layer.jpg
1319 ms
navi-bim.png
1966 ms
media_nav.png
2946 ms
flags.png
2017 ms
map-australia.png
2197 ms
map-south-america.png
1879 ms
map-north-america.png
2913 ms
map-africa.png
2054 ms
map-asia.png
2311 ms
map-europe.png
2718 ms
map-all.png
2228 ms
logo_obo.png
2370 ms
thinkconnected.png
2422 ms
lub2016_DE_stage.jpg
6115 ms
bg_button.png
2547 ms
icon-arrow-right.png
2598 ms
analytics.js
22 ms
collect
13 ms
collect
97 ms
xml_lang.xml
2900 ms
60-Jahre-Unterflur_stage.jpg
3129 ms
OBO-Construct_stage.jpg
4304 ms
ga-audiences
37 ms
Montagefilm-Quick-Pipe_stage.jpg
3843 ms
shadow_main-feature.png
2727 ms
video_play.png
2872 ms
UDhome-Familie_teaser-02.jpg
2888 ms
Blitzschut-Leitfaden_teaser.jpg
3048 ms
das-ist-obo_teaser.jpg
3133 ms
slider_pause-play.png
2932 ms
white.png
3059 ms
progress-bar.png
3054 ms
close.png
797 ms
common.js
22 ms
util.js
45 ms
stats.js
42 ms
AuthenticationService.Authenticate
112 ms
obo.de 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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
obo.de 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
Page has valid source maps
obo.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Obo.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Obo.de 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.
obo.de
Open Graph description is not detected on the main page of OBO. 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: