Tools & Wizards About Us
mobile-seo.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobile-seo.de

Mobile SEO

Page Load Speed

5.6 sec in total

First Response

366 ms

Resources Loaded

3 sec

Page Rendered

2.2 sec

mobile-seo.de screenshot

About Website

Welcome to mobile-seo.de homepage info - get ready to check Mobile SEO best content for Germany right away, or after learning these important things about mobile-seo.de

Visit mobile-seo.de

Key Findings

We analyzed Mobile-seo.de page load time and found that the first response time was 366 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

mobile-seo.de performance score

0

Network Requests Diagram

mobile-seo.de

366 ms

www.mobile-seo.de

1089 ms

booster_cache&nocache=1341844209

309 ms

booster_cache&nocache=1341844209

312 ms

jquery.min.js

33 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 64% of them (25 requests) were addressed to the original Mobile-seo.de, 10% (4 requests) were made to Google-analytics.com and 5% (2 requests) were made to Count.gjuce.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mobile-seo.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 532.8 kB (33%)

Content Size

1.6 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile-seo.de main page is 1.6 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. 30% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 47.9 kB

  • Original 63.1 kB
  • After minification 58.7 kB
  • After compression 15.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. 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 47.9 kB or 76% of the original size.

Image Optimization

-19%

Potential reduce by 196.3 kB

  • Original 1.1 MB
  • After minification 857.2 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, Mobile SEO needs image optimization as it can save up to 196.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-57%

Potential reduce by 237.3 kB

  • Original 419.1 kB
  • After minification 408.7 kB
  • After compression 181.8 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 237.3 kB or 57% of the original size.

CSS Optimization

-75%

Potential reduce by 51.3 kB

  • Original 68.2 kB
  • After minification 57.2 kB
  • After compression 16.9 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. Mobile-seo.de needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (31%)

Requests Now

36

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile SEO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mobile-seo.de

mobile-seo.de

366 ms

www.mobile-seo.de

www.mobile-seo.de

1089 ms

booster_cache&nocache=1341844209

booster_cache&nocache=1341844209

309 ms

booster_cache&nocache=1341844209

booster_cache&nocache=1341844209

312 ms

jquery.min.js

jquery.min.js

33 ms

booster_cache&js_minify=0&nocache=1341844209

booster_cache&js_minify=0&nocache=1341844209

610 ms

dlbutton02.php

dlbutton02.php

306 ms

gjuce.gif

gjuce.gif

155 ms

mobile.gif

mobile.gif

151 ms

m-169x300.png

m-169x300.png

495 ms

1507758_915011891843855_6362920858754101976_n2-168x300.jpg

1507758_915011891843855_6362920858754101976_n2-168x300.jpg

152 ms

smartphone-errors1.png

smartphone-errors1.png

409 ms

mobile-url-in-mobile-serp-200x300.png

mobile-url-in-mobile-serp-200x300.png

547 ms

Foto9-169x300.png

Foto9-169x300.png

509 ms

Foto10-169x300.png

Foto10-169x300.png

338 ms

Foto11-169x300.png

Foto11-169x300.png

516 ms

Foto12-169x300.png

Foto12-169x300.png

547 ms

Bildschirmfoto-2013-07-05-um-16.53.15.png

Bildschirmfoto-2013-07-05-um-16.53.15.png

1027 ms

Bildschirmfoto-2013-07-05-um-17.26.51.png

Bildschirmfoto-2013-07-05-um-17.26.51.png

895 ms

Bildschirmfoto-2013-07-05-um-17.14.37.png

Bildschirmfoto-2013-07-05-um-17.14.37.png

1015 ms

Bildschirmfoto-2013-07-05-um-17.25.23.png

Bildschirmfoto-2013-07-05-um-17.25.23.png

926 ms

Bildschirmfoto-2013-02-21-um-17.24.33-300x294.png

Bildschirmfoto-2013-02-21-um-17.24.33-300x294.png

744 ms

Bildschirmfoto-2013-02-26-um-11.06.32-300x71.png

Bildschirmfoto-2013-02-26-um-11.06.32-300x71.png

650 ms

intel-appup.gif

intel-appup.gif

763 ms

twitter.png

twitter.png

846 ms

rss-icon.png

rss-icon.png

863 ms

ga.js

ga.js

30 ms

raphaelicons-webfont.woff

raphaelicons-webfont.woff

898 ms

piwik.js

piwik.js

550 ms

__utm.gif

__utm.gif

13 ms

css

css

51 ms

font-awesome.css

font-awesome.css

7 ms

embed_button-81a8d3bee604d45bad2c528af77556bf2e00bb7503e870da19cdaaf156399a17.css

embed_button-81a8d3bee604d45bad2c528af77556bf2e00bb7503e870da19cdaaf156399a17.css

75 ms

pwat_button-480fffcd9334c1f3a6126654311d02bbb2bea57765b8c45dde85aa0ea9cf8849.js

pwat_button-480fffcd9334c1f3a6126654311d02bbb2bea57765b8c45dde85aa0ea9cf8849.js

81 ms

analytics.js

analytics.js

38 ms

collect

collect

18 ms

nr-885.min.js

nr-885.min.js

42 ms

96dde036b8

96dde036b8

57 ms

piwik.php

piwik.php

159 ms

SEO Factors

mobile-seo.de SEO score

0

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile-seo.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 Mobile-seo.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.

Social Sharing Optimization

mobile-seo.de

Open Graph description is not detected on the main page of Mobile SEO. 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: