Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

802.be

Value-added distributor 802 Networks: wireless & IP camera configuration, installation, and support

Page Load Speed

2.1 sec in total

First Response

287 ms

Resources Loaded

1.5 sec

Page Rendered

355 ms

802.be screenshot

About Website

Welcome to 802.be homepage info - get ready to check 802 best content right away, or after learning these important things about 802.be

Value-added distributor 802 Networks: wireless & IP camera configuration, installation, and support

Visit 802.be

Key Findings

We analyzed 802.be page load time and found that the first response time was 287 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

802.be performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value6,980 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

802.be

287 ms

pompiedoe.nl

540 ms

alles-voor-de-zomer2.jpg

168 ms

badmode.jpg

259 ms

lingerie.jpg

258 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original 802.be, 87% (20 requests) were made to Pompiedoe.nl and 4% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (568 ms) relates to the external source Pompiedoe.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.1 kB (83%)

Content Size

301.2 kB

After Optimization

51.1 kB

In fact, the total size of 802.be main page is 301.2 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. CSS take 253.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 40.5 kB

  • Original 47.2 kB
  • After minification 34.6 kB
  • After compression 6.6 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 12.6 kB, which is 27% 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 40.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 648 B
  • After minification 648 B

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. 802 images are well optimized though.

CSS Optimization

-83%

Potential reduce by 209.6 kB

  • Original 253.4 kB
  • After minification 245.5 kB
  • After compression 43.8 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. 802.be needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 802. According to our analytics all requests are already optimized.

Accessibility Review

802.be accessibility score

88

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-hidden="true"] elements contain focusable descendents

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.

Best Practices

802.be 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

High

Page has valid source maps

SEO Factors

802.be SEO score

93

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

Links do not have descriptive text

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

    NL

  • Encoding

    UTF-8

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

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