Tools & Wizards About Us
ioff.de screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

ioff.de

IOFF - Das Medienforum

Page Load Speed

5.3 sec in total

First Response

232 ms

Resources Loaded

4.8 sec

Page Rendered

262 ms

ioff.de screenshot

About Website

Click here to check amazing IOFF content for Germany. Otherwise, check out these important facts you probably never knew about ioff.de

Inoffizielles Fernseh- & Medien-Forum: 'Second Screen' seit Ende 2000! Mit zahlreichen Boards und vielen Beiträgen zu TV und Medien. Diskussionen rund um das Thema Fernsehen, Medien, Internet. (Ehemal...

Visit ioff.de

Key Findings

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

Performance Metrics

ioff.de performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

ioff.de

232 ms

www.ioff.de

222 ms

www.ioff.de

730 ms

style.css

458 ms

overlay.js

482 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 38% of them (21 requests) were addressed to the original Ioff.de, 53% (29 requests) were made to Img.ioff.de and 4% (2 requests) were made to Nerdic.h5v.eu. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Img.ioff.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.1 kB (43%)

Content Size

259.1 kB

After Optimization

148.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ioff.de main page is 259.1 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. 20% of websites need less resources to load. HTML takes 108.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 91.7 kB

  • Original 108.2 kB
  • After minification 96.7 kB
  • After compression 16.5 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 11.5 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 91.7 kB or 85% of the original size.

Image Optimization

-28%

Potential reduce by 18.0 kB

  • Original 64.2 kB
  • After minification 46.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. Obviously, IOFF needs image optimization as it can save up to 18.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 1.4 kB

  • Original 86.2 kB
  • After minification 86.2 kB
  • After compression 84.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 13 B

  • Original 449 B
  • After minification 449 B
  • After compression 436 B

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. Ioff.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (75%)

Requests Now

51

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ioff.de

ioff.de

232 ms

www.ioff.de

www.ioff.de

222 ms

www.ioff.de

www.ioff.de

730 ms

style.css

style.css

458 ms

overlay.js

overlay.js

482 ms

vbulletin-core.js

vbulletin-core.js

526 ms

css.php

css.php

709 ms

jquery.min.js

jquery.min.js

42 ms

cookiebanner.js

cookiebanner.js

841 ms

moli_es5.min.js

moli_es5.min.js

786 ms

moli.min.mjs

moli.min.mjs

1107 ms

script.js

script.js

87 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

437 ms

css.php

css.php

590 ms

css.php

css.php

661 ms

vbulletin-sidebar.js

vbulletin-sidebar.js

487 ms

css.php

css.php

1052 ms

vbulletin_md5.js

vbulletin_md5.js

946 ms

js

js

82 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

575 ms

connection-min.js

connection-min.js

526 ms

animation-min.js

animation-min.js

408 ms

close_popup.png

close_popup.png

365 ms

avatar106754_1.gif

avatar106754_1.gif

490 ms

avatar42440_126.gif

avatar42440_126.gif

404 ms

avatar56927_40.gif

avatar56927_40.gif

420 ms

avatar106890_1.gif

avatar106890_1.gif

459 ms

avatar47408_121.gif

avatar47408_121.gif

449 ms

avatar27006_75.gif

avatar27006_75.gif

476 ms

avatar79610_4.gif

avatar79610_4.gif

806 ms

ioff_logo_eye180.png

ioff_logo_eye180.png

558 ms

navbit-home.png

navbit-home.png

419 ms

collapse_40b.png

collapse_40b.png

519 ms

forum_old-48.png

forum_old-48.png

481 ms

lastpost-right.png

lastpost-right.png

484 ms

subforum_old-48.png

subforum_old-48.png

723 ms

category_forum_old-48.png

category_forum_old-48.png

812 ms

icon10.gif

icon10.gif

866 ms

forum_stats.png

forum_stats.png

871 ms

birthday.png

birthday.png

899 ms

legend.png

legend.png

958 ms

forum_new-16.png

forum_new-16.png

1092 ms

forum_old-16.png

forum_old-16.png

1189 ms

category-16.png

category-16.png

1257 ms

forum_link-16.png

forum_link-16.png

1251 ms

tab-collapsed.png

tab-collapsed.png

1305 ms

widget-forum.png

widget-forum.png

1348 ms

widget-comment.png

widget-comment.png

1473 ms

unknown.gif

unknown.gif

1573 ms

sp.gif

sp.gif

1650 ms

nav-icons-bg.png

nav-icons-bg.png

1618 ms

black_downward_arrow.png

black_downward_arrow.png

1696 ms

notice-exclamation.png

notice-exclamation.png

1727 ms

rss_40b.png

rss_40b.png

1831 ms

open-sans-v15-latin-regular.woff

open-sans-v15-latin-regular.woff

1930 ms

Accessibility Review

ioff.de accessibility score

58

Accessibility Issues

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

[role]s do not have all required [aria-*] attributes

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.

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

ioff.de best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ioff.de 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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ioff.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 Ioff.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ioff.de

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