Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 55% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

aios.be

AIOS - Let us handle your IT

Page Load Speed

6 sec in total

First Response

362 ms

Resources Loaded

5.3 sec

Page Rendered

333 ms

aios.be screenshot

About Website

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

All In One Systems is uw leverancier voor computers, monitoren, printers en meer. Voor 15.00 uur besteld, de volgende werkdag in huis.

Visit aios.be

Key Findings

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

Performance Metrics

aios.be performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.218

57/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

aios.be

362 ms

aios.be

530 ms

882dcdd81281a67d780fb2d1aa8897e8.min.css

683 ms

styles-l.min.css

593 ms

require.min.js

497 ms

Our browser made a total of 252 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Aios.be, 81% (205 requests) were made to Static.aios.be and 8% (20 requests) were made to Media.aios.be. The less responsive or slowest element that took the longest time to load (889 ms) relates to the external source Scontent-ams2-1.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.7 kB (15%)

Content Size

2.4 MB

After Optimization

2.1 MB

In fact, the total size of Aios.be main page is 2.4 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

-87%

Potential reduce by 150.9 kB

  • Original 172.5 kB
  • After minification 168.9 kB
  • After compression 21.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. 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 150.9 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 102.5 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. AIOS images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.0 kB

  • Original 366.6 kB
  • After minification 366.5 kB
  • After compression 361.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-58%

Potential reduce by 98.3 kB

  • Original 168.7 kB
  • After minification 74.5 kB
  • After compression 70.4 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. Aios.be needs all CSS files to be minified and compressed as it can save up to 98.3 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 202 (89%)

Requests Now

227

After Optimization

25

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

Accessibility Review

aios.be accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aios.be 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 Aios.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 AIOS. 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: