Tools & Wizards About Us
ooowiki.de screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

ooowiki.de

Archiv des LibreOffice- und OpenOffice.org-Wiki

Page Load Speed

1.5 sec in total

First Response

296 ms

Resources Loaded

1.1 sec

Page Rendered

103 ms

ooowiki.de screenshot

About Website

Visit ooowiki.de now to see the best up-to-date Ooo Wiki content for Germany and also check out these interesting facts you probably never knew about ooowiki.de

Das Archiv bietet Grundlagenwissen, Anleitungen, Tipps, Vorlagen und Makros für OpenOffice.org und LibreOffice.

Visit ooowiki.de

Key Findings

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

Performance Metrics

ooowiki.de performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.381

27/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

ooowiki.de

296 ms

www.ooowiki.de

337 ms

common.css

96 ms

screen.css

190 ms

logo.png

374 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 73% of them (8 requests) were addressed to the original Ooowiki.de, 18% (2 requests) were made to Fonts.googleapis.com and 9% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (374 ms) belongs to the original domain Ooowiki.de.

Page Optimization Overview & Recommendations

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

Content Size

25.3 kB

After Optimization

16.9 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-71%

Potential reduce by 5.0 kB

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 2.0 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 5.0 kB or 71% of the original size.

Image Optimization

-18%

Potential reduce by 3.3 kB

  • Original 17.9 kB
  • After minification 14.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. Obviously, Ooo Wiki needs image optimization as it can save up to 3.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-20%

Potential reduce by 77 B

  • Original 392 B
  • After minification 352 B
  • After compression 315 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. Ooowiki.de needs all CSS files to be minified and compressed as it can save up to 77 B or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • Images
  • CSS

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

Network Requests Diagram

ooowiki.de

ooowiki.de

296 ms

www.ooowiki.de

www.ooowiki.de

337 ms

common.css

common.css

96 ms

screen.css

screen.css

190 ms

logo.png

logo.png

374 ms

icon-info.png

icon-info.png

193 ms

css

css

23 ms

css

css

38 ms

help.svg

help.svg

97 ms

ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff

ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff

32 ms

print.css

print.css

98 ms

Accessibility Review

ooowiki.de accessibility score

90

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ooowiki.de best practices score

75

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

SEO Factors

ooowiki.de SEO score

85

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

High

Page is blocked from indexing

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

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ooowiki.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ooowiki.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

ooowiki.de

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