Tools & Wizards About Us
imos.net screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    32% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 91

    SEO

    Google-friendlier than
    76% of websites

imos.net

imos. Alles Internet. Außer gewöhnlich. Internetagentur aus Göppingen. imos

Page Load Speed

5.8 sec in total

First Response

574 ms

Resources Loaded

3 sec

Page Rendered

2.2 sec

imos.net screenshot

About Website

Visit imos.net now to see the best up-to-date Imos content for Germany and also check out these interesting facts you probably never knew about imos.net

Brauchen Sie eine schnelle und stabile Internet-Anbindung? Oder einen begeisternden Online-Auftritt? Soll Ihr E-Shop so richtig durchstarten? imos verleiht Ihrem Webauftritt Kraft. Bei uns ist eben al...

Visit imos.net

Key Findings

We analyzed Imos.net page load time and found that the first response time was 574 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. This domain responded with an error, which can significantly jeopardize Imos.net rating and web reputation

Performance Metrics

imos.net performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value7,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

www.imos.net

574 ms

version-4.css

505 ms

default.js

720 ms

default_javascript.js

235 ms

conversion.js

15 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 65% of them (20 requests) were addressed to the original Imos.net, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Gtrk.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Imos.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 563.9 kB (22%)

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imos.net main page is 2.5 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 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 80.9 kB

  • Original 97.5 kB
  • After minification 82.3 kB
  • After compression 16.6 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 15.2 kB, which is 16% 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 80.9 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Imos images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 301.6 kB

  • Original 454.4 kB
  • After minification 454.4 kB
  • After compression 152.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 301.6 kB or 66% of the original size.

CSS Optimization

-88%

Potential reduce by 178.9 kB

  • Original 203.0 kB
  • After minification 162.5 kB
  • After compression 24.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. Imos.net needs all CSS files to be minified and compressed as it can save up to 178.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (25%)

Requests Now

24

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.imos.net

www.imos.net

574 ms

version-4.css

version-4.css

505 ms

default.js

default.js

720 ms

default_javascript.js

default_javascript.js

235 ms

conversion.js

conversion.js

15 ms

analytics.js

analytics.js

117 ms

logo.gif

logo.gif

168 ms

191 ms

9012.js

9012.js

78 ms

logo.svg

logo.svg

130 ms

internetseiten.jpg

internetseiten.jpg

548 ms

online-shops.jpg

online-shops.jpg

1013 ms

richtfunk.jpg

richtfunk.jpg

1282 ms

fallback.jpg

fallback.jpg

1385 ms

loading.gif

loading.gif

524 ms

fb-like.svg

fb-like.svg

527 ms

facebook.svg

facebook.svg

543 ms

bg-3.jpg

bg-3.jpg

851 ms

bg-8.jpg

bg-8.jpg

1007 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

564 ms

DroidSans-Bold-webfont.woff

DroidSans-Bold-webfont.woff

735 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

820 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

924 ms

collect

collect

15 ms

collect

collect

371 ms

352 ms

s

s

240 ms

t.js

t.js

229 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

501 ms

u

u

226 ms

js

js

79 ms

Accessibility Review

imos.net accessibility score

76

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

imos.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

imos.net SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Imos.net 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 Imos.net 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

imos.net

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