Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

wesio.de

DEWEZET - Aktuelle Nachrichten der Deister- und Weserzeitung I dewezet.de

Page Load Speed

20.6 sec in total

First Response

368 ms

Resources Loaded

19.6 sec

Page Rendered

626 ms

wesio.de screenshot

About Website

Click here to check amazing Wesio content. Otherwise, check out these important facts you probably never knew about wesio.de

Das Nachrichtenportal für Hameln, Weserbergland, Lokalsport, Politik, Wirtschaft & Wissenschaft. Informationen über Veranstaltungen, Kultur, Hannover 96.

Visit wesio.de

Key Findings

We analyzed Wesio.de page load time and found that the first response time was 368 ms and then it took 20.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

wesio.de performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value18.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value20.7 s

0/100

25%

SI (Speed Index)

Value21.6 s

0/100

10%

TBT (Total Blocking Time)

Value8,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value36.8 s

0/100

10%

Network Requests Diagram

wesio.de

368 ms

www.wesio.de

428 ms

startseite.html

14952 ms

style_25.css

423 ms

system.js

210 ms

Our browser made a total of 283 requests to load all elements on the main page. We found that 83% of them (235 requests) were addressed to the original Wesio.de, 8% (23 requests) were made to Maps.google.com and 3% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (15 sec) belongs to the original domain Wesio.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 973.1 kB (34%)

Content Size

2.8 MB

After Optimization

1.9 MB

In fact, the total size of Wesio.de main page is 2.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 495.5 kB

  • Original 545.2 kB
  • After minification 544.8 kB
  • After compression 49.7 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 495.5 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 35.6 kB

  • Original 1.7 MB
  • After minification 1.6 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. Wesio images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 319.6 kB

  • Original 488.6 kB
  • After minification 488.0 kB
  • After compression 169.1 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 319.6 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 122.4 kB

  • Original 147.7 kB
  • After minification 146.2 kB
  • After compression 25.3 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. Wesio.de needs all CSS files to be minified and compressed as it can save up to 122.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (16%)

Requests Now

274

After Optimization

229

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

Accessibility Review

wesio.de accessibility score

54

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

[aria-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

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

wesio.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

wesio.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

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

    N/A

  • Encoding

    ISO-8859-15

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wesio.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 Wesio.de main page’s claimed encoding is iso-8859-15. 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

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