Tools & Wizards About Us
opendi.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

opendi.de

Telefonbuch - Open Directory

Page Load Speed

2 sec in total

First Response

219 ms

Resources Loaded

1.2 sec

Page Rendered

578 ms

opendi.de screenshot

About Website

Welcome to opendi.de homepage info - get ready to check Open Di best content for Germany right away, or after learning these important things about opendi.de

Telefonauskunft zu gewerblichen und privaten Adressen und Personensuche bei Opendi. Alle Kontakte können kostenlos angerufen werden.

Visit opendi.de

Key Findings

We analyzed Opendi.de page load time and found that the first response time was 219 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

opendi.de performance score

0

Network Requests Diagram

opendi.de

219 ms

www.opendi.de

232 ms

style.css

151 ms

css

23 ms

css

22 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 16% of them (3 requests) were addressed to the original Opendi.de, 37% (7 requests) were made to D1adm8u512yvme.cloudfront.net and 11% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (406 ms) relates to the external source Code.etracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.2 kB (42%)

Content Size

308.5 kB

After Optimization

178.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Opendi.de main page is 308.5 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. 25% of websites need less resources to load. Javascripts take 180.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.8 kB

  • Original 17.2 kB
  • After minification 14.7 kB
  • After compression 4.4 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.5 kB, which is 15% 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 12.8 kB or 74% of the original size.

Image Optimization

-10%

Potential reduce by 8.9 kB

  • Original 91.6 kB
  • After minification 82.7 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. Open Di images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 92.7 kB

  • Original 180.3 kB
  • After minification 180.2 kB
  • After compression 87.6 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 92.7 kB or 51% of the original size.

CSS Optimization

-81%

Potential reduce by 15.8 kB

  • Original 19.4 kB
  • After minification 11.8 kB
  • After compression 3.6 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. Opendi.de needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (41%)

Requests Now

17

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Di. 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 as a result speed up the page load time.

Network Requests Diagram

opendi.de

opendi.de

219 ms

www.opendi.de

www.opendi.de

232 ms

style.css

style.css

151 ms

css

css

23 ms

css

css

22 ms

px.js

px.js

11 ms

px.js

px.js

11 ms

jquery.min.js

jquery.min.js

23 ms

e.js

e.js

363 ms

logo_stern.png

logo_stern.png

184 ms

home_map.png

home_map.png

338 ms

home_logo_text.png

home_logo_text.png

185 ms

home_teaser_right.png

home_teaser_right.png

174 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

386 ms

261 ms

t.js

t.js

406 ms

home_teaser_bg.png

home_teaser_bg.png

135 ms

analytics.js

analytics.js

14 ms

collect

collect

10 ms

SEO Factors

opendi.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 Opendi.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 Opendi.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

opendi.de

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