4.3 sec in total
926 ms
2.9 sec
414 ms
Visit m.obermain.de now to see the best up-to-date M Obermain content for United States and also check out these interesting facts you probably never knew about m.obermain.de
Visit m.obermain.deWe analyzed M.obermain.de page load time and found that the first response time was 926 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
m.obermain.de performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value15.0 s
0/100
25%
Value9.4 s
12/100
10%
Value1,060 ms
25/100
30%
Value0.368
29/100
15%
Value15.2 s
7/100
10%
926 ms
31 ms
128 ms
198 ms
197 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 53% of them (57 requests) were addressed to the original M.obermain.de, 14% (15 requests) were made to Dmp.theadex.com and 11% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (926 ms) belongs to the original domain M.obermain.de.
Page size can be reduced by 286.8 kB (35%)
815.1 kB
528.3 kB
In fact, the total size of M.obermain.de main page is 815.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 413.5 kB which makes up the majority of the site volume.
Potential reduce by 51.4 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 8.7 kB, which is 14% 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 51.4 kB or 81% of the original size.
Potential reduce by 1.0 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. M Obermain images are well optimized though.
Potential reduce by 203.4 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 203.4 kB or 68% of the original size.
Potential reduce by 31.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. M.obermain.de needs all CSS files to be minified and compressed as it can save up to 31.0 kB or 79% of the original size.
Number of requests can be reduced by 53 (59%)
90
37
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Obermain. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
m.obermain.de
926 ms
css
31 ms
10_m_basic_32.css
128 ms
13_m_layout_32.css
198 ms
12_m_navigation_32.css
197 ms
11_m_elements_32.css
199 ms
init.js
316 ms
bootstrap.min.js
30 ms
3_jquery.scrollDirection.js
201 ms
4_m_obermain.js
223 ms
omsv_container_151.js
272 ms
dynamicobjectloader.js
292 ms
5_cookiechoices.js
292 ms
js.js
102 ms
extlib_prototype.js
223 ms
extlib_scriptaculous.js
239 ms
extlib_jquery.js
321 ms
fcmsLib_Core.js
244 ms
analytics.js
29 ms
24838_3_Obermain-Tagblatt.jpg
104 ms
441748_m3t1w480h270q75v16428_1LIFF5.jpg
105 ms
441736_0_1LINRW.jpg
103 ms
441703_0_1LD7KJ.jpg
104 ms
441719_2_1LIPIB.jpg
104 ms
441398_2_1LIF56.jpg
164 ms
441718_m3t1w480h270q75v62609_1LIPD4.jpg
201 ms
441678_2_1LIM19.jpg
199 ms
412122_0_1J5ZC3.jpg
199 ms
441676_0_1LIKK4.jpg
202 ms
441731_m3t1w480h270q75v49501_1LIPS4.jpg
299 ms
441730_0_1LIPJG.jpg
262 ms
441729_0_1LHXRA.jpg
296 ms
441684_m2t1h270q75v37623_1LIOCM.jpg
297 ms
441648_0_1LILAG.jpg
299 ms
441594_0_1LIJ8Z.jpg
300 ms
429652_m3t1w480h270q75s1v57841_Fantalk_20Obersdorf_202.jpg
360 ms
428307_m3t1w480h270q75v52022_KAG2256.jpg
394 ms
428287_m3t1w480h270q75v37349_uetzing_20frosch.jpg
396 ms
427228_m3t1w480h270q75v8794_mistelfeld1.jpg
399 ms
425808_m3t1w480h270q75v52542_15.jpg
401 ms
441724_m3t1w480h270q75s1v23677_1LIPMZ.jpg
401 ms
441695_2_1LINEE.jpg
491 ms
441704_m3t1w480h270q75v11425_1LIN1U.jpg
496 ms
441702_0_1LIKQB.jpg
496 ms
441388_0_1LIEWJ.jpg
496 ms
442163_m3t1w480h270q75v42822_urn-newsml-dpa-com-20090101-160319-99-284889_large_4_3.jpg
496 ms
442160_0_urn-newsml-dpa-com-20090101-160319-99-284333_large_4_3.jpg
496 ms
442156_0_urn-newsml-dpa-com-20090101-160319-99-284861_large_4_3.jpg
555 ms
442141_0_urn-newsml-dpa-com-20090101-160319-99-284682_large_4_3.jpg
590 ms
AKu1CjQ4qnV8MUltkAX3sFBI1aZvkJLeFEwcwXkBYq0.ttf
30 ms
6LmGj5dOJopQKEkt88GowQNd2zpumJ3ZXdYPaAdqT7w.ttf
30 ms
6LmGj5dOJopQKEkt88GowfqJSHIsY8pKqTgTouATXAk.ttf
30 ms
6LmGj5dOJopQKEkt88GowfIJfOcmuekKI9HFvv_Ow38.ttf
31 ms
RFda8w1V0eDZheqfcyQ4EInF5uFdDttMLvmWuJdhhgs.ttf
41 ms
ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf
31 ms
ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf
31 ms
ZvcMqxEwPfh2qDWBPxn6nvzeo8SCrGyBsNQUDsw2Qr8.ttf
30 ms
fontello.woff
571 ms
collect
37 ms
nAqt4hiqwq3tzCecpgPmVZK-EqCRAgJ4DGsxXn5jo_s.ttf
7 ms
3Mz4hOHzs2npRMG3B1ascbearE5_VzBcjtDoaNr3b3c.ttf
30 ms
nAqt4hiqwq3tzCecpgPmVQqfFxSJsGWORebWzQ_6S3g.ttf
29 ms
nAqt4hiqwq3tzCecpgPmVcn79XP5f7_gPslCYOZ5R-k.ttf
29 ms
fcmsUser_User.js
553 ms
fcmsUser_Customer.js
547 ms
fcmsUser_Navigation.js
549 ms
rc
227 ms
26865,26867,26869,26871
101 ms
rta.js
25 ms
default.js
169 ms
ci
218 ms
adex.js
253 ms
p.min.js
12 ms
gpt.js
7 ms
pubads_impl_82.js
7 ms
data
350 ms
container.html
40 ms
ads
523 ms
fcmsLib_Utils.js
306 ms
fcp.gif
216 ms
t.js
132 ms
fcmsUser_Core.js
137 ms
fcmsUser_Utils.js
130 ms
fcmsUser_Statistic.js
133 ms
fcmsUser_Layout.js
121 ms
analytic.js
85 ms
121 ms
1.gif
171 ms
2.gif
182 ms
adex.js
181 ms
adrtxtag.min.js
201 ms
271 ms
pixel
15 ms
extlib_iscroll.js
125 ms
pixel
14 ms
cm.gif
90 ms
2.gif
90 ms
2.gif
89 ms
analytic.js
85 ms
85 ms
1.gif
90 ms
300x250
216 ms
osd.js
14 ms
pixel
14 ms
cm.gif
88 ms
2.gif
91 ms
2.gif
88 ms
m.obermain.de 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.
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.
m.obermain.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
m.obermain.de 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
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.obermain.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 M.obermain.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.
m.obermain.de
Open Graph description is not detected on the main page of M Obermain. 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: