Tools & Wizards About Us
prieurestgery.be screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prieurestgery.be

Le Prieuré Saint-Géry - Restaurant gastronomique

Page Load Speed

5.6 sec in total

First Response

207 ms

Resources Loaded

4.5 sec

Page Rendered

955 ms

prieurestgery.be screenshot

About Website

Click here to check amazing Prieurestgery content. Otherwise, check out these important facts you probably never knew about prieurestgery.be

Vincent Gardinal, chef-propriétaire du restaurant Le Prieuré Saint Gery, vous accueille dans son établissement depuis 1996.

Visit prieurestgery.be

Key Findings

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

prieurestgery.be performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.077

95/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

prieurestgery.be

207 ms

prieurestgery.be

2276 ms

style.min.css

170 ms

styles.css

257 ms

extendify-utilities.css

277 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 64% of them (68 requests) were addressed to the original Prieurestgery.be, 9% (10 requests) were made to Fonts.gstatic.com and 7% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Prieurestgery.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.4 kB (18%)

Content Size

1.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prieurestgery.be main page is 1.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. 80% 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. Javascripts take 692.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 79.3 kB

  • Original 102.1 kB
  • After minification 100.4 kB
  • After compression 22.8 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 79.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 107 B

  • Original 419.2 kB
  • After minification 419.1 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. Prieurestgery images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 113.5 kB

  • Original 692.7 kB
  • After minification 649.2 kB
  • After compression 579.2 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 113.5 kB or 16% of the original size.

CSS Optimization

-29%

Potential reduce by 64.6 kB

  • Original 221.0 kB
  • After minification 220.0 kB
  • After compression 156.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. Prieurestgery.be needs all CSS files to be minified and compressed as it can save up to 64.6 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (76%)

Requests Now

91

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prieurestgery.be

prieurestgery.be

207 ms

prieurestgery.be

prieurestgery.be

2276 ms

style.min.css

style.min.css

170 ms

styles.css

styles.css

257 ms

extendify-utilities.css

extendify-utilities.css

277 ms

styles.css

styles.css

262 ms

settings.css

settings.css

350 ms

style.min.css

style.min.css

351 ms

style.min.css

style.min.css

367 ms

front.min.css

front.min.css

357 ms

js_composer.min.css

js_composer.min.css

559 ms

addtoany.min.css

addtoany.min.css

370 ms

lightgallery.css

lightgallery.css

448 ms

font-awesome.min.css

font-awesome.min.css

451 ms

icomoon.css

icomoon.css

456 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

466 ms

style.css

style.css

545 ms

style.css

style.css

531 ms

user.css

user.css

576 ms

page.js

page.js

41 ms

jquery.min.js

jquery.min.js

589 ms

jquery-migrate.min.js

jquery-migrate.min.js

604 ms

addtoany.min.js

addtoany.min.js

619 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

658 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

687 ms

app.js

app.js

775 ms

front.min.js

front.min.js

691 ms

modernizr.custom.js

modernizr.custom.js

652 ms

css

css

34 ms

prettyPhoto.min.css

prettyPhoto.min.css

643 ms

owl.min.css

owl.min.css

684 ms

animate.min.css

animate.min.css

687 ms

css

css

18 ms

index.js

index.js

704 ms

index.js

index.js

685 ms

api.js

api.js

44 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

831 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

832 ms

wp-polyfill.min.js

wp-polyfill.min.js

831 ms

index.js

index.js

832 ms

plugins.js

plugins.js

833 ms

TweenMax.min.js

TweenMax.min.js

832 ms

jquery.countdown.min.js

jquery.countdown.min.js

736 ms

jquery.mCustomScrollbar.min.js

jquery.mCustomScrollbar.min.js

708 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

706 ms

lightgallery-all.min.js

lightgallery-all.min.js

741 ms

script.js

script.js

618 ms

js_composer_front.min.js

js_composer_front.min.js

674 ms

waypoints.min.js

waypoints.min.js

667 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

742 ms

owl.carousel.min.js

owl.carousel.min.js

740 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

661 ms

underscore.min.js

underscore.min.js

672 ms

vc_grid.min.js

vc_grid.min.js

674 ms

akismet-frontend.js

akismet-frontend.js

647 ms

forms.js

forms.js

617 ms

eso.BRQnzO8v.js

eso.BRQnzO8v.js

18 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf

20 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDXbtY.ttf

24 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf

31 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf

30 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDXbtY.ttf

30 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtY.ttf

30 ms

Prieure-Saint-Gery-logo.png

Prieure-Saint-Gery-logo.png

400 ms

Prieure-Saint-Gery-logo.png

Prieure-Saint-Gery-logo.png

160 ms

Prieure-Saint-Gery-logo.png

Prieure-Saint-Gery-logo.png

398 ms

gery_03.png

gery_03.png

236 ms

gery_03.png

gery_03.png

400 ms

banner-prieure-homepage-80-1.jpg

banner-prieure-homepage-80-1.jpg

510 ms

vincent-gardinal-prieure-saint-gery-chef-etoile-1.jpg

vincent-gardinal-prieure-saint-gery-chef-etoile-1.jpg

404 ms

hostellerie-prieure-saint-gery-chef-etoile-1.jpg

hostellerie-prieure-saint-gery-chef-etoile-1.jpg

640 ms

home-page-prieure-saint-gery-1.jpg

home-page-prieure-saint-gery-1.jpg

640 ms

horizontal-gauche-prieure-saint-gery-1-1.jpg

horizontal-gauche-prieure-saint-gery-1-1.jpg

508 ms

horizontal-hostellerie-prieure-saint-gery.jpg

horizontal-hostellerie-prieure-saint-gery.jpg

705 ms

signature-tars.svg

signature-tars.svg

508 ms

embed

embed

213 ms

sdk.js

sdk.js

45 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

641 ms

icomoon.ttf

icomoon.ttf

588 ms

recaptcha__en.js

recaptcha__en.js

82 ms

zOL64pLDlL1D99S8g8PtiKchq-dmiA.ttf

zOL64pLDlL1D99S8g8PtiKchq-dmiA.ttf

65 ms

sdk.js

sdk.js

33 ms

Prieure-Saint-Gery-logo.png

Prieure-Saint-Gery-logo.png

499 ms

gery_03.png

gery_03.png

424 ms

js

js

160 ms

sm.25.html

sm.25.html

138 ms

anchor

anchor

95 ms

styles__ltr.css

styles__ltr.css

65 ms

recaptcha__en.js

recaptcha__en.js

68 ms

JmauVxhhvNeGRVvMjuhavwcr4cbjHfJOauIT80S7Fws.js

JmauVxhhvNeGRVvMjuhavwcr4cbjHfJOauIT80S7Fws.js

151 ms

webworker.js

webworker.js

152 ms

logo_48.png

logo_48.png

139 ms

page.php

page.php

228 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

127 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

128 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

128 ms

recaptcha__en.js

recaptcha__en.js

73 ms

eOzOzediAge.css

eOzOzediAge.css

68 ms

VWDhCULazb5.js

VWDhCULazb5.js

95 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

94 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

124 ms

5xOV5e9oy4e.js

5xOV5e9oy4e.js

128 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

127 ms

p55HfXW__mM.js

p55HfXW__mM.js

126 ms

438914919_746234694288766_7321135856226980921_n.jpg

438914919_746234694288766_7321135856226980921_n.jpg

241 ms

438094456_746235300955372_1700085288668923405_n.jpg

438094456_746235300955372_1700085288668923405_n.jpg

39 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

20 ms

Accessibility Review

prieurestgery.be accessibility score

85

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.

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

<frame> or <iframe> elements do not have a title

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

prieurestgery.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

SEO Factors

prieurestgery.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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

prieurestgery.be

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