Tools & Wizards About Us
huibert-aalbers.com screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

huibert-aalbers.com

Huibert Aalbers

Page Load Speed

2 sec in total

First Response

213 ms

Resources Loaded

1.6 sec

Page Rendered

108 ms

huibert-aalbers.com screenshot

About Website

Welcome to huibert-aalbers.com homepage info - get ready to check Huibert Aalbers best content right away, or after learning these important things about huibert-aalbers.com

This is the resume of Huibert Aalbers. I am a Software IT Architect working at IBM, specialized in databases, development and system integration.

Visit huibert-aalbers.com

Key Findings

We analyzed Huibert-aalbers.com page load time and found that the first response time was 213 ms and then it took 1.7 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

huibert-aalbers.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.732

6/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

huibert-aalbers.com

213 ms

huibert-aalbers.com

283 ms

urchin.js

6 ms

styles.css

70 ms

colourtag-page18.css

137 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 59% of them (44 requests) were addressed to the original Huibert-aalbers.com, 24% (18 requests) were made to Platform.twitter.com and 8% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (592 ms) belongs to the original domain Huibert-aalbers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.3 kB (10%)

Content Size

4.6 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Huibert-aalbers.com main page is 4.6 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 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 17.6 kB

  • Original 22.6 kB
  • After minification 21.1 kB
  • After compression 5.0 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 17.6 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 360.9 kB

  • Original 4.4 MB
  • After minification 4.0 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. Huibert Aalbers images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 59.1 kB

  • Original 208.9 kB
  • After minification 208.9 kB
  • After compression 149.8 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 59.1 kB or 28% of the original size.

CSS Optimization

-40%

Potential reduce by 5.8 kB

  • Original 14.3 kB
  • After minification 14.2 kB
  • After compression 8.5 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. Huibert-aalbers.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 40% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (71%)

Requests Now

69

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

huibert-aalbers.com

huibert-aalbers.com

213 ms

huibert-aalbers.com

huibert-aalbers.com

283 ms

urchin.js

urchin.js

6 ms

styles.css

styles.css

70 ms

colourtag-page18.css

colourtag-page18.css

137 ms

flexslider.css

flexslider.css

200 ms

css

css

24 ms

css

css

40 ms

css

css

43 ms

css

css

43 ms

css

css

44 ms

css

css

46 ms

navnum.css

navnum.css

198 ms

bannerb.css

bannerb.css

197 ms

sson.css

sson.css

197 ms

title60.css

title60.css

202 ms

side18.css

side18.css

264 ms

ec16.css

ec16.css

265 ms

fontquestrial.css

fontquestrial.css

264 ms

fontquestrialslogan.css

fontquestrialslogan.css

264 ms

fontquestrialec.css

fontquestrialec.css

263 ms

fontquestrialnav.css

fontquestrialnav.css

268 ms

fontspinside.css

fontspinside.css

330 ms

fontarialtext.css

fontarialtext.css

330 ms

sidebarnone.css

sidebarnone.css

330 ms

corange.css

corange.css

331 ms

javascript.js

javascript.js

331 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

400 ms

function.js

function.js

396 ms

jquery.fitvids.js

jquery.fitvids.js

396 ms

jquery.flexslider.js

jquery.flexslider.js

397 ms

stacks.css

stacks.css

397 ms

stacks_page_page18.css

stacks_page_page18.css

399 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

528 ms

jquery-ui.min.js

jquery-ui.min.js

592 ms

stacks_page_page18.js

stacks_page_page18.js

463 ms

widgets.js

widgets.js

14 ms

__utm.gif

__utm.gif

16 ms

tutorial.jpg

tutorial.jpg

75 ms

stacks-image-40ab678.jpg

stacks-image-40ab678.jpg

133 ms

stacks-image-9beb126.jpg

stacks-image-9beb126.jpg

130 ms

shadow.png

shadow.png

74 ms

stacks-image-d7c2eb1.jpg

stacks-image-d7c2eb1.jpg

132 ms

stacks-image-27003a4.jpg

stacks-image-27003a4.jpg

131 ms

stacks-image-bda7368.jpg

stacks-image-bda7368.jpg

197 ms

QdVUSTchPBm7nuUeVf70viFg.ttf

QdVUSTchPBm7nuUeVf70viFg.ttf

30 ms

Utrecht.jpg

Utrecht.jpg

504 ms

Geneve.jpg

Geneve.jpg

388 ms

Madrid.jpg

Madrid.jpg

443 ms

Bayonne.jpg

Bayonne.jpg

505 ms

Bordeaux.jpg

Bordeaux.jpg

340 ms

Montreal.jpg

Montreal.jpg

448 ms

MexicoCity.jpg

MexicoCity.jpg

388 ms

yql

yql

31 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

29 ms

settings

settings

132 ms

socialico-webfont.woff

socialico-webfont.woff

390 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

2 ms

huibert

huibert

70 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

2 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

16 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

20 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

20 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

43 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

42 ms

_buildManifest.js

_buildManifest.js

54 ms

_ssgManifest.js

_ssgManifest.js

42 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

10 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

11 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

2 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

7 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

6 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

18 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

5 ms

Accessibility Review

huibert-aalbers.com accessibility score

76

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

Best Practices

huibert-aalbers.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

huibert-aalbers.com SEO score

80

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

huibert-aalbers.com

Open Graph data is detected on the main page of Huibert Aalbers. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: