Tools & Wizards About Us
grace-hollogne.be screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

grace-hollogne.be

Site de gracehollogne

Page Load Speed

3.1 sec in total

First Response

474 ms

Resources Loaded

2.3 sec

Page Rendered

344 ms

grace-hollogne.be screenshot

About Website

Welcome to grace-hollogne.be homepage info - get ready to check Grace Hollogne best content for Belgium right away, or after learning these important things about grace-hollogne.be

Site Internet de l'Administration communale de Grâce-Hollogne. Bienvenue

Visit grace-hollogne.be

Key Findings

We analyzed Grace-hollogne.be page load time and found that the first response time was 474 ms and then it took 2.6 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

grace-hollogne.be performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

grace-hollogne.be

474 ms

base.css

80 ms

public.css

158 ms

columns.css

157 ms

authoring.css

164 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Grace-hollogne.be and no external sources were called. The less responsive or slowest element that took the longest time to load (853 ms) belongs to the original domain Grace-hollogne.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 71.7 kB (11%)

Content Size

639.3 kB

After Optimization

567.6 kB

  • HTML
  • Images

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

HTML Optimization

-85%

Potential reduce by 46.7 kB

  • Original 54.8 kB
  • After minification 45.6 kB
  • After compression 8.1 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 9.2 kB, which is 17% 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 46.7 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 25.0 kB

  • Original 584.5 kB
  • After minification 559.5 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. Grace Hollogne images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 48 (74%)

Requests Now

65

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grace-hollogne.be

grace-hollogne.be

474 ms

base.css

base.css

80 ms

public.css

public.css

158 ms

columns.css

columns.css

157 ms

authoring.css

authoring.css

164 ms

portlets.css

portlets.css

164 ms

controlpanel.css

controlpanel.css

164 ms

print.css

print.css

161 ms

deprecated.css

deprecated.css

233 ms

navtree.css

navtree.css

235 ms

invisibles.css

invisibles.css

251 ms

forms.css

forms.css

236 ms

dropdown-menu.css

dropdown-menu.css

239 ms

ploneKss.css

ploneKss.css

238 ms

maps.css

maps.css

319 ms

popoll.css

popoll.css

311 ms

++resource++contentleadimage.css

++resource++contentleadimage.css

311 ms

cpskin3.css

cpskin3.css

314 ms

cpskin3_nav.css

cpskin3_nav.css

313 ms

cpskin3_themes.css

cpskin3_themes.css

328 ms

cpskin3_theme0.css

cpskin3_theme0.css

400 ms

cpskin3_theme1_section.css

cpskin3_theme1_section.css

388 ms

cpskin3_theme2_section.css

cpskin3_theme2_section.css

389 ms

cpskin3_theme3_section.css

cpskin3_theme3_section.css

390 ms

cpskin3_theme4_section.css

cpskin3_theme4_section.css

394 ms

cpskin3_theme5_section.css

cpskin3_theme5_section.css

404 ms

cpskin3_theme0_section.css

cpskin3_theme0_section.css

499 ms

accordion.css

accordion.css

498 ms

comarquage.css

comarquage.css

467 ms

ploneCustom.css

ploneCustom.css

471 ms

jquery-cachekey4531.js

jquery-cachekey4531.js

557 ms

sarissa-cachekey0620.js

sarissa-cachekey0620.js

481 ms

resourcekukit-cachekey0135.js

resourcekukit-cachekey0135.js

630 ms

resourcedropdown-menu-cachekey2521.js

resourcedropdown-menu-cachekey2521.js

549 ms

fckeditor-cachekey5096.js

fckeditor-cachekey5096.js

567 ms

accordion-cachekey8709.js

accordion-cachekey8709.js

576 ms

site-bg.gif

site-bg.gif

135 ms

logo.png

logo.png

238 ms

banner.jpg

banner.jpg

689 ms

search-bg.png

search-bg.png

354 ms

input_background.gif

input_background.gif

187 ms

loupe.png

loupe.png

224 ms

lien-accueil.png

lien-accueil.png

290 ms

theme1-bg.gif

theme1-bg.gif

337 ms

theme2-bg.gif

theme2-bg.gif

346 ms

theme3-bg.gif

theme3-bg.gif

350 ms

theme4-bg.gif

theme4-bg.gif

375 ms

content-bord-left.png

content-bord-left.png

420 ms

content-bord-right.png

content-bord-right.png

428 ms

focus-bottom.gif

focus-bottom.gif

436 ms

linkTransparent.gif

linkTransparent.gif

441 ms

image_preview

image_preview

559 ms

actus.gif

actus.gif

506 ms

rss.gif

rss.gif

516 ms

image_thumb

image_thumb

524 ms

image_thumb

image_thumb

606 ms

image_thumb

image_thumb

593 ms

events.gif

events.gif

600 ms

image_preview

image_preview

689 ms

path2607.png

path2607.png

759 ms

image_preview

image_preview

775 ms

image_preview

image_preview

779 ms

top-calendrier.gif

top-calendrier.gif

693 ms

bottom-calendrier.gif

bottom-calendrier.gif

767 ms

image_preview

image_preview

853 ms

image_thumb

image_thumb

783 ms

spinner.gif

spinner.gif

847 ms

Accessibility Review

grace-hollogne.be accessibility score

82

Accessibility Issues

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

grace-hollogne.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

grace-hollogne.be SEO score

77

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

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

grace-hollogne.be

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