Tools & Wizards About Us
mobilonly.de screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

mobilonly.de

mobile only SI GmbH

Page Load Speed

3.8 sec in total

First Response

733 ms

Resources Loaded

2.8 sec

Page Rendered

252 ms

mobilonly.de screenshot

About Website

Welcome to mobilonly.de homepage info - get ready to check Mobilonly best content right away, or after learning these important things about mobilonly.de

mobile Apps für den Außendienst in den Bereichen Vertrieb und Service

Visit mobilonly.de

Key Findings

We analyzed Mobilonly.de page load time and found that the first response time was 733 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mobilonly.de performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,620 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value1.534

0/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

mobileonly.com

733 ms

style.css

350 ms

styles.css

352 ms

shCore.css

353 ms

shCoreDefault.css

352 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mobilonly.de, 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (733 ms) relates to the external source Mobileonly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.0 kB (27%)

Content Size

1.2 MB

After Optimization

863.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobilonly.de main page is 1.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. 40% of websites need less resources to load. Images take 804.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 18.8 kB

  • Original 23.7 kB
  • After minification 21.0 kB
  • After compression 4.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 2.6 kB, which is 11% 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 18.8 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 37.3 kB

  • Original 804.8 kB
  • After minification 767.6 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. Mobilonly images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 153.0 kB

  • Original 219.9 kB
  • After minification 217.9 kB
  • After compression 66.9 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 153.0 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 117.0 kB

  • Original 141.3 kB
  • After minification 133.0 kB
  • After compression 24.3 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. Mobilonly.de needs all CSS files to be minified and compressed as it can save up to 117.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (44%)

Requests Now

34

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobileonly.com

mobileonly.com

733 ms

style.css

style.css

350 ms

styles.css

styles.css

352 ms

shCore.css

shCore.css

353 ms

shCoreDefault.css

shCoreDefault.css

352 ms

shThemeDefault.css

shThemeDefault.css

357 ms

jquery.js

jquery.js

221 ms

jquery-migrate.min.js

jquery-migrate.min.js

211 ms

jquery.min.js

jquery.min.js

39 ms

bootstrap.min.js

bootstrap.min.js

357 ms

functional.css

functional.css

451 ms

style-light.css

style-light.css

450 ms

jquery.form.min.js

jquery.form.min.js

454 ms

scripts.js

scripts.js

452 ms

wp-embed.min.js

wp-embed.min.js

209 ms

all.frontend.min.js

all.frontend.min.js

458 ms

bootstrap.min.css

bootstrap.min.css

222 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

107 ms

logo.png

logo.png

154 ms

slide_motrade.png

slide_motrade.png

410 ms

slideshow_molager.png

slideshow_molager.png

426 ms

slide_moscanner.png

slide_moscanner.png

518 ms

slide_moservice.png

slide_moservice.png

517 ms

motrade.png

motrade.png

311 ms

moservice.png

moservice.png

512 ms

molager.png

molager.png

519 ms

mowebshop.png

mowebshop.png

513 ms

anpassung_icon.png

anpassung_icon.png

516 ms

kompatibilitaet_icon.png

kompatibilitaet_icon.png

615 ms

service-beratung_icon.png

service-beratung_icon.png

616 ms

entwicklung_icon.png

entwicklung_icon.png

619 ms

BVMW.png

BVMW.png

617 ms

loading-icon-128x128.gif

loading-icon-128x128.gif

567 ms

light-arrows.png

light-arrows.png

569 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

668 ms

Accessibility Review

mobilonly.de accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

mobilonly.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mobilonly.de SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilonly.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Mobilonly.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

mobilonly.de

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