Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

vintagehotel.be

Vintage Hotel Brussels | OFFICIAL SITE | Boutique Hotel Brussels Centre

Page Load Speed

3 sec in total

First Response

160 ms

Resources Loaded

2.1 sec

Page Rendered

696 ms

vintagehotel.be screenshot

About Website

Visit vintagehotel.be now to see the best up-to-date Vintage Hotel content for France and also check out these interesting facts you probably never knew about vintagehotel.be

Welcome to the Vintage Hotel, a small boutique hotel in Brussels city center, steps from the fashionable Avenue Louise. Try Glamping in the Vintage Airstream Room, a very unique experience! Official w...

Visit vintagehotel.be

Key Findings

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

vintagehotel.be performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value10.0 s

0/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value5,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

www.vintagehotel.be

160 ms

Ed1ZHGApYYRBx2Y5P282OrQrcHs1FbqGADMdgSOOdw9fenCffFHN4UJLFRbh52jhWD9uwh9DjDZyZQsKwe4cjR9owQ9UZe9h5gT8iaiaO1ZTd1syZhmGdas8dfoKZPUh-AoXjAi8-eNXZA30jc9Cdcmaic80ieB1ZAyziemCO1FUiABkZWF3jAF8OcFzdP37Oco8iaZTd1syZhmGdas8dfoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPJ4Z1mXiW4yOWgXH6qJtKGbMg62JMJ7fbKzMsMMeMb6MKG4fHXgIMMjgKMfH6qJK3IbMg6YJMJ7fbRRHyMMeMX6MKG4fOMgIMMj2KMfH6qJn6IbMg6bJMJ7fbKwMsMMegI6MKG4fJsmIMIjgfMfH6qJxubbMs6BJMJ7fbKgmsMgeMS6MKG4fJmmIMIj2KMfH6qJ689bMs6sJMHbMS5DK7GB.js

62 ms

css

46 ms

localize.js

84 ms

jquery-ui-1.8.16.custom.css

576 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Vintagehotel.be, 45% (33 requests) were made to Static1.squarespace.com and 20% (15 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (830 ms) relates to the external source Static.cubilis.eu.

Page Optimization Overview & Recommendations

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

Content Size

2.8 MB

After Optimization

2.6 MB

In fact, the total size of Vintagehotel.be main page is 2.8 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. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 116.1 kB

  • Original 139.0 kB
  • After minification 127.7 kB
  • After compression 22.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. 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 116.1 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 133.6 kB

  • Original 2.5 MB
  • After minification 2.4 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. Vintage Hotel images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 33.2 kB

  • Original 173.2 kB
  • After minification 173.2 kB
  • After compression 140.0 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 33.2 kB or 19% of the original size.

CSS Optimization

-0%

Potential reduce by 14 B

  • Original 4.6 kB
  • After minification 4.6 kB
  • After compression 4.6 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. Vintagehotel.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (25%)

Requests Now

59

After Optimization

44

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

Accessibility Review

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

[id] attributes on active, focusable elements are not unique

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

vintagehotel.be SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Vintagehotel.be 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 Vintagehotel.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 data is detected on the main page of Vintage Hotel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: