3.1 sec in total
273 ms
2.5 sec
348 ms
Click here to check amazing SAmobile content. Otherwise, check out these important facts you probably never knew about samobile.de
, Rheda-Wiedenbrück
Visit samobile.deWe analyzed Samobile.de page load time and found that the first response time was 273 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
samobile.de performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value4.1 s
48/100
25%
Value5.3 s
58/100
10%
Value40 ms
100/100
30%
Value0.105
88/100
15%
Value4.3 s
85/100
10%
273 ms
105 ms
193 ms
193 ms
210 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 58% of them (14 requests) were addressed to the original Samobile.de, 8% (2 requests) were made to 1und1-premiumpartner.de and 8% (2 requests) were made to E-seller.de. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source 1und1-premiumpartner.de.
Page size can be reduced by 61.5 kB (14%)
447.3 kB
385.8 kB
In fact, the total size of Samobile.de main page is 447.3 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. 15% of websites need less resources to load. Images take 422.1 kB which makes up the majority of the site volume.
Potential reduce by 3.9 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 924 B, which is 17% 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 3.9 kB or 73% of the original size.
Potential reduce by 40.3 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. SAmobile images are well optimized though.
Potential reduce by 4.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 4.1 kB or 83% of the original size.
Potential reduce by 13.2 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. Samobile.de needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 88% of the original size.
Number of requests can be reduced by 7 (37%)
19
12
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAmobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
samobile.de
273 ms
main.css
105 ms
colorscheme.css
193 ms
style.css
193 ms
live_tinc.js
210 ms
banner.php3
988 ms
468x601276602729.jpg
253 ms
pagebg.gif
109 ms
menubg.gif
113 ms
n1active.gif
104 ms
n1.gif
102 ms
_wsb_keyvisual.jpg
212 ms
submenubg.gif
213 ms
sn1.gif
208 ms
BannerSAadresse+Kopie.jpg
624 ms
_wsb_793x1122_FlyerM$C3$A4rz2013.jpg
725 ms
banner.php3
1084 ms
error_empty.gif
109 ms
error_empty.gif
109 ms
468x601276602729.jpg
529 ms
466 ms
000000664114.gif
834 ms
152 ms
10218566.gif
291 ms
samobile.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
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.
samobile.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
Page has valid source maps
samobile.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
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Samobile.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Samobile.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.
samobile.de
Open Graph description is not detected on the main page of SAmobile. 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: