Tools & Wizards About Us
beaware.be screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

beaware.be

be.aware: a Webstation on human issues and values against facts and junk

Page Load Speed

3.5 sec in total

First Response

572 ms

Resources Loaded

2.7 sec

Page Rendered

168 ms

beaware.be screenshot

About Website

Visit beaware.be now to see the best up-to-date Be Aware content and also check out these interesting facts you probably never knew about beaware.be

A human touch and a place of values in a world of facts and plenty of junk, read the Bee-lines and post your own in the Bee-talk forum

Visit beaware.be

Key Findings

We analyzed Beaware.be page load time and found that the first response time was 572 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

beaware.be performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

beaware.be

572 ms

not_found

781 ms

aggregator.css

195 ms

book.css

201 ms

node.css

206 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Beaware.be, 93% (38 requests) were made to Abitmore.be and 5% (2 requests) were made to Openclipart.org. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Abitmore.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.8 kB (43%)

Content Size

212.3 kB

After Optimization

121.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Beaware.be main page is 212.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. 15% of websites need less resources to load. Images take 86.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.3 kB

  • Original 15.0 kB
  • After minification 14.2 kB
  • After compression 3.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 11.3 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 1.4 kB

  • Original 86.6 kB
  • After minification 85.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. Be Aware images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 37.0 kB

  • Original 57.7 kB
  • After minification 45.8 kB
  • After compression 20.7 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 37.0 kB or 64% of the original size.

CSS Optimization

-77%

Potential reduce by 41.1 kB

  • Original 53.0 kB
  • After minification 38.9 kB
  • After compression 12.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. Beaware.be needs all CSS files to be minified and compressed as it can save up to 41.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (87%)

Requests Now

38

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

beaware.be

beaware.be

572 ms

not_found

not_found

781 ms

aggregator.css

aggregator.css

195 ms

book.css

book.css

201 ms

node.css

node.css

206 ms

defaults.css

defaults.css

202 ms

system.css

system.css

202 ms

system-menus.css

system-menus.css

203 ms

user.css

user.css

388 ms

content-module.css

content-module.css

401 ms

dhtml_menu.css

dhtml_menu.css

401 ms

simplemenu-22aa9f21d8577f71387d630e93f53934.css

simplemenu-22aa9f21d8577f71387d630e93f53934.css

396 ms

original.css

original.css

403 ms

simplenews.css

simplenews.css

401 ms

fieldgroup.css

fieldgroup.css

582 ms

views.css

views.css

588 ms

printlinks.css

printlinks.css

600 ms

layout.css

layout.css

598 ms

graphics.css

graphics.css

603 ms

typography.css

typography.css

602 ms

links.css

links.css

782 ms

giordani.css

giordani.css

780 ms

jquery.js

jquery.js

882 ms

drupal.js

drupal.js

795 ms

dhtml_menu.js

dhtml_menu.js

797 ms

external.js

external.js

802 ms

simplemenu.js

simplemenu.js

975 ms

superfish-1.4.1.js

superfish-1.4.1.js

978 ms

simplemenu-f85b95bdb1067a1139312e3d34c6e8a9.js

simplemenu-f85b95bdb1067a1139312e3d34c6e8a9.js

1004 ms

image-missing.png

image-missing.png

33 ms

body.gif

body.gif

106 ms

rotate.php

rotate.php

298 ms

bgblock.gif

bgblock.gif

102 ms

leaf.gif

leaf.gif

195 ms

collapsed.gif

collapsed.gif

200 ms

print_icon.gif

print_icon.gif

203 ms

pdf_icon.gif

pdf_icon.gif

304 ms

tags.gif

tags.gif

309 ms

right-green.gif

right-green.gif

370 ms

down-green.gif

down-green.gif

365 ms

image-missing.png

image-missing.png

49 ms

Accessibility Review

beaware.be accessibility score

92

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

beaware.be best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

beaware.be SEO score

71

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

beaware.be

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