Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

webawere.nl

WebOké.nl | Professionele Hosting voor Budgetprijzen

Page Load Speed

2.7 sec in total

First Response

100 ms

Resources Loaded

2.4 sec

Page Rendered

136 ms

webawere.nl screenshot

About Website

Welcome to webawere.nl homepage info - get ready to check Web Awere best content for Netherlands right away, or after learning these important things about webawere.nl

Betrouwbare Nederlandse hosting zonder verrassingen, al sinds 2004. WebOké biedt hosting aan voor de állerbeste prijs-kwaliteitverhouding.

Visit webawere.nl

Key Findings

We analyzed Webawere.nl page load time and found that the first response time was 100 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

webawere.nl performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

hostedby

100 ms

style.css

87 ms

index.php

607 ms

addthis_widget.js

21 ms

overlibmws.js

173 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Webawere.nl, 7% (3 requests) were made to S7.addthis.com and 5% (2 requests) were made to M.addthis.com. The less responsive or slowest element that took the longest time to load (648 ms) relates to the external source Web-oke.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 552.7 kB (64%)

Content Size

860.5 kB

After Optimization

307.7 kB

In fact, the total size of Webawere.nl main page is 860.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 724.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 70.9 kB

  • Original 101.4 kB
  • After minification 98.6 kB
  • After compression 30.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. 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 70.9 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 1.3 kB

  • Original 21.0 kB
  • After minification 19.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. Web Awere images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 469.1 kB

  • Original 724.6 kB
  • After minification 722.4 kB
  • After compression 255.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 469.1 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 11.5 kB

  • Original 13.5 kB
  • After minification 10.2 kB
  • After compression 2.0 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. Webawere.nl needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (43%)

Requests Now

40

After Optimization

23

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

Accessibility Review

webawere.nl accessibility score

76

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

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.

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 IDs are not unique

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

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

webawere.nl 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

webawere.nl SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    NL

  • Language Claimed

    NL

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webawere.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Webawere.nl 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

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