Tools & Wizards About Us
owad.de screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

owad.de

OWAD - One Word A Day

Page Load Speed

2.4 sec in total

First Response

532 ms

Resources Loaded

1.8 sec

Page Rendered

115 ms

owad.de screenshot

About Website

Visit owad.de now to see the best up-to-date OWAD content for Switzerland and also check out these interesting facts you probably never knew about owad.de

Build your wordpower with Paul Smith

Visit owad.de

Key Findings

We analyzed Owad.de page load time and found that the first response time was 532 ms and then it took 1.9 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

owad.de performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.2 s

92/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value3.5 s

92/100

10%

Network Requests Diagram

owad.de

532 ms

abc-owad.css

214 ms

urchin.js

5 ms

cookieconsent.latest.min.js

14 ms

show_ads.js

5 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 56% of them (22 requests) were addressed to the original Owad.de, 10% (4 requests) were made to Pagead2.googlesyndication.com and 10% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (781 ms) belongs to the original domain Owad.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.2 kB (25%)

Content Size

296.1 kB

After Optimization

220.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 13.2 kB

  • Original 18.3 kB
  • After minification 15.6 kB
  • After compression 5.1 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.7 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 13.2 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 8.3 kB

  • Original 180.5 kB
  • After minification 172.2 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. OWAD images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 46.1 kB

  • Original 88.6 kB
  • After minification 88.5 kB
  • After compression 42.5 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 46.1 kB or 52% of the original size.

CSS Optimization

-87%

Potential reduce by 7.5 kB

  • Original 8.6 kB
  • After minification 7.2 kB
  • After compression 1.1 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. Owad.de needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

owad.de

owad.de

532 ms

abc-owad.css

abc-owad.css

214 ms

urchin.js

urchin.js

5 ms

cookieconsent.latest.min.js

cookieconsent.latest.min.js

14 ms

show_ads.js

show_ads.js

5 ms

jquery.min.js

jquery.min.js

31 ms

jquery.rsv-2.5.1.min.js

jquery.rsv-2.5.1.min.js

227 ms

__utm.gif

__utm.gif

10 ms

zrt_lookup.html

zrt_lookup.html

24 ms

show_ads_impl.js

show_ads_impl.js

42 ms

topnav-logo-owad.jpg

topnav-logo-owad.jpg

219 ms

google-plus.png

google-plus.png

220 ms

facebook.png

facebook.png

223 ms

twitter.png

twitter.png

220 ms

spacer.gif

spacer.gif

221 ms

style.paul.jpg

style.paul.jpg

303 ms

button_startseite.png

button_startseite.png

434 ms

style.button.gif

style.button.gif

436 ms

stern.gif

stern.gif

437 ms

wdr.gif

wdr.gif

436 ms

cosmopolitan.gif

cosmopolitan.gif

438 ms

br3-wdw.gif

br3-wdw.gif

523 ms

neologo.gif

neologo.gif

645 ms

woerterbuchinfo.gif

woerterbuchinfo.gif

649 ms

flagge_klein_de.jpg

flagge_klein_de.jpg

650 ms

flagge_klein_grau_en.jpg

flagge_klein_grau_en.jpg

652 ms

googleplus.jpg

googleplus.jpg

654 ms

ads

ads

150 ms

spacer.green.gif

spacer.green.gif

656 ms

topnav-banner-owad.jpg

topnav-banner-owad.jpg

781 ms

osd.js

osd.js

22 ms

piwik.js

piwik.js

488 ms

10255011681070850687

10255011681070850687

32 ms

abg.js

abg.js

34 ms

m_js_controller.js

m_js_controller.js

52 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

18 ms

s

s

18 ms

x_button_blue2.png

x_button_blue2.png

19 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

3 ms

Accessibility Review

owad.de accessibility score

69

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

owad.de best practices score

75

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

SEO Factors

owad.de SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Owad.de can be misinterpreted by Google and other search engines. Our service has detected that English 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 Owad.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

owad.de

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