5.8 sec in total
737 ms
4.6 sec
466 ms
Visit imobilestore.de now to see the best up-to-date IMobile Store content and also check out these interesting facts you probably never knew about imobilestore.de
iMobile Store
Visit imobilestore.deWe analyzed Imobilestore.de page load time and found that the first response time was 737 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
imobilestore.de performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value8.1 s
2/100
25%
Value9.2 s
13/100
10%
Value380 ms
70/100
30%
Value1.303
1/100
15%
Value12.2 s
15/100
10%
737 ms
204 ms
318 ms
206 ms
317 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 85% of them (82 requests) were addressed to the original Imobilestore.de, 4% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Imobilestore.de.
Page size can be reduced by 1.5 MB (39%)
3.8 MB
2.3 MB
In fact, the total size of Imobilestore.de main page is 3.8 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. 60% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 133.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 133.3 kB or 78% of the original size.
Potential reduce by 327.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. Obviously, IMobile Store needs image optimization as it can save up to 327.8 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 935.1 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 935.1 kB or 73% of the original size.
Potential reduce by 55.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. Imobilestore.de needs all CSS files to be minified and compressed as it can save up to 55.5 kB or 74% of the original size.
Number of requests can be reduced by 43 (47%)
91
48
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMobile Store. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
imobilestore.de
737 ms
skeleton.css
204 ms
style.css
318 ms
flexslider.css
206 ms
color.css
317 ms
layout.css
212 ms
css
25 ms
bjqs.css
305 ms
slidestyle.css
314 ms
jquery-ui.css
5 ms
elastislide.css
321 ms
custom.css
421 ms
jquery-1.8.2.js
1183 ms
jquery-ui-1.9.0.custom.min.js
1244 ms
jquery-ui-tabs-rotate.js
425 ms
bjqs-1.3.min.js
426 ms
modernizr.custom.17475.js
427 ms
colorbox.css
541 ms
jquery.colorbox.js
556 ms
addthis_widget.js
8 ms
hoverIntent.js
240 ms
superfish.js
265 ms
supersubs.js
339 ms
tinynav.min.js
350 ms
custom.js
362 ms
bottom.css
370 ms
jquery.js
28 ms
jquery.jcarousel.min.js
445 ms
jquery.pikachoose.min.js
456 ms
jquery.touchwipe.min.js
465 ms
slidorion.css
478 ms
jquery.easing.js
542 ms
jquery.slidorion.min.js
564 ms
menu.css
566 ms
stimenu.css
592 ms
jquery.easing.1.3.js
643 ms
jquery.iconmenu.js
668 ms
header.jpg
224 ms
img-sprite.png
108 ms
termin.png
104 ms
place.png
115 ms
1420583373.PNG
1253 ms
1409241751.jpg
312 ms
1409242473.jpg
433 ms
1420554666.jpg
433 ms
1431898548.jpg
231 ms
1431898381.jpg
316 ms
1431898292.jpg
336 ms
1408950533.jpg
535 ms
1408950998.jpg
530 ms
1428264217.jpg
918 ms
1428263919.jpg
747 ms
1425421617.jpg
756 ms
1428264727.jpg
856 ms
1422907113.jpg
852 ms
1422900334.jpg
856 ms
1421317497.png
2788 ms
1422900556.jpg
958 ms
1408949358.jpg
1067 ms
1408949606.jpg
1065 ms
pic4.jpg
1033 ms
pic5.jpg
1065 ms
logo-footer.png
1136 ms
list-arrow.gif
1171 ms
payment%20icon.png
1175 ms
youtube.png
1171 ms
twitter.png
1238 ms
google.png
1274 ms
facebook.png
1278 ms
base.css
1251 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
9 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
17 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
21 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
16 ms
like.php
159 ms
qeKvIRsJabD.js
135 ms
LVx-xkvaJ0b.png
147 ms
300lo.json
53 ms
home.png
133 ms
iphone.png
131 ms
smartphone.png
132 ms
tablet.png
130 ms
Accessories.png
131 ms
pricelist.png
200 ms
about%20us.png
221 ms
handlar.png
225 ms
contact.png
222 ms
overlay.png
226 ms
controls.png
297 ms
border.png
309 ms
loading_background.png
322 ms
loading.gif
316 ms
pause.png
438 ms
loading.gif
396 ms
sh.8e5f85691f9aaa082472a194.html
37 ms
layers.e5ea973510bf60b3db41.js
9 ms
imobilestore.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
imobilestore.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
imobilestore.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imobilestore.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Imobilestore.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.
imobilestore.de
Open Graph description is not detected on the main page of IMobile Store. 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: