Tools & Wizards About Us
imaginate.be screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

imaginate.be

Zonnepanelen en Elektriciteitswerken - Imaginate Electrics | Zonnepanelen & elektriciteit

Page Load Speed

2.6 sec in total

First Response

279 ms

Resources Loaded

2.2 sec

Page Rendered

164 ms

imaginate.be screenshot

About Website

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

U wil graag zonnepanelen laten plaatsen? Een slimme keuze! Door een PV systeem bespaar je meer dan ooit flink op je energiefactuur. Tevens kunnen we de

Visit imaginate.be

Key Findings

We analyzed Imaginate.be page load time and found that the first response time was 279 ms and then it took 2.4 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

imaginate.be performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.355

31/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

imaginate.be

279 ms

www.imaginate-electrics.be

281 ms

plusone.js

90 ms

prototype.js

255 ms

scriptaculous.js

164 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Imaginate.be, 41% (14 requests) were made to Imaginate-electrics.be and 29% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (626 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.0 kB (40%)

Content Size

492.3 kB

After Optimization

297.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imaginate.be main page is 492.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. 30% of websites need less resources to load. Javascripts take 244.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.1 kB

  • Original 13.0 kB
  • After minification 11.6 kB
  • After compression 3.9 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 1.5 kB, which is 11% 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 9.1 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 322 B

  • Original 233.1 kB
  • After minification 232.8 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. Imaginate images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 184.4 kB

  • Original 244.5 kB
  • After minification 183.2 kB
  • After compression 60.1 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 184.4 kB or 75% of the original size.

CSS Optimization

-66%

Potential reduce by 1.1 kB

  • Original 1.6 kB
  • After minification 1.4 kB
  • After compression 559 B

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. Imaginate.be needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (58%)

Requests Now

31

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imaginate.be

imaginate.be

279 ms

www.imaginate-electrics.be

www.imaginate-electrics.be

281 ms

plusone.js

plusone.js

90 ms

prototype.js

prototype.js

255 ms

scriptaculous.js

scriptaculous.js

164 ms

lightbox.js

lightbox.js

165 ms

lightbox.css

lightbox.css

167 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

effects.js

effects.js

86 ms

builder.js

builder.js

83 ms

ga.js

ga.js

10 ms

header.png

header.png

328 ms

01.jpg

01.jpg

163 ms

02.jpg

02.jpg

164 ms

15.jpg

15.jpg

164 ms

regstat.aspx

regstat.aspx

293 ms

dot_vert.gif

dot_vert.gif

164 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

3 ms

loading.gif

loading.gif

163 ms

closelabel.gif

closelabel.gif

167 ms

likebox.php

likebox.php

85 ms

hDvwL1_H7g-.css

hDvwL1_H7g-.css

292 ms

56WNbrUYLbL.css

56WNbrUYLbL.css

362 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

496 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

626 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

520 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

521 ms

belcounter_black.gif

belcounter_black.gif

83 ms

1461221_10151869099973380_319831027_n.jpg

1461221_10151869099973380_319831027_n.jpg

355 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

74 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

74 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

71 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

73 ms

Accessibility Review

imaginate.be accessibility score

83

Accessibility Issues

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

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

imaginate.be best practices score

83

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

Page has valid source maps

SEO Factors

imaginate.be SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imaginate.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Imaginate.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

imaginate.be

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