Analyze

brugge.com: book your stay at bruges

Page load speed analysis

  • 61/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    423 ms

  • Resources loaded

    13.5 sec

  • Page rendered

    623 ms

  • Total page load time

    14.6 sec

Click here to check amazing Brugge content. Otherwise, check out these important facts you probably never knew about brugge.com

We analyzed Brugge.com page load time and found that the first response time was 423 ms and then it took 14.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Page optimization

  • HTML 11.5 kB
    Images 1.8 MB
    Javascripts 1.7 kB
    CSS 42.7 kB

    In fact, the total size of Brugge.com main page is 1.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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

    • Original 11.5 kB
    • After minification 10.4 kB
    • After compression 1.9 kB

    HTML optimization

    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 9.6 kB or 84% of the original size.

    • Original 1.8 MB
    • After optimization 1.8 MB

    Image optimization

    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. Brugge images are well optimized though.

    • Original 1.7 kB
    • After minification 1.4 kB
    • After compression 396 B

    JavaScript optimization

    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 1.3 kB or 77% of the original size.

    • Original 42.7 kB
    • After minification 35.5 kB
    • After compression 9.1 kB

    CSS optimization

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

Network requests diagram

  • brugge.com
  • hotels.brugge.com
  • jquery-ui.css
  • jquery-1.10.2.js
  • jquery-ui.js
  • styles.css
  • mediaqueries.css
  • scripts.js
  • css
  • ui-bg_flat_75_ffffff_40x100.png
  • brugge.jpg
  • brugge_small.jpg
  • blankenberge_small.jpg
  • oostende_small.jpg
  • knokke_small.jpg
  • nieuwpoort_small.jpg
  • roeselare_small.jpg
  • logo_booking.png
  • KYNzioYhDai7mTMnx_gDgoB9a16epZVaac-gfobfbfA.ttf
  • 11EDm-lum6tskJMBbdy9aYbHQgMiPeC0S_y2k9np4ck.ttf
  • 11EDm-lum6tskJMBbdy9ac5nNYjIb-KbqEh50utxFtk.ttf
  • 11EDm-lum6tskJMBbdy9aX726VmFjkD_1knHNL407_k.ttf

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Brugge.com, 55% (12 requests) were made to Hotels.brugge.com and 18% (4 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (12.4 sec) relates to the external source Hotels.brugge.com.

Additional info on brugge.com

Requests

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

3

Javascripts

9

Images

4

CSS

16

All

Possible request optimization

3

Javascripts

9

Images

1

CSS

3

Optimized

13

All

Good result

Redirects

As for redirects, our browser was forwarded to http://hotels.brugge.com/ before it reached this domain.

IP address

Brugge.com uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

DNS records

Type Host Target/ip TTL Other
A

brugge.com

212.123.3.108 3600
NS

brugge.com

ns3.westsite.be 3600
NS

brugge.com

ns1.westsite.be 3600
NS

brugge.com

ns2.westsite.be 3600
SOA

brugge.com

3600 Mname: ns1.westsite.be
Rname: tech.westsite.be
Serial: 2013030400
Refresh: 28800
Retry: 7200
Expire: 1209600
Minimum-ttl: 3600

Language and encoding

Normal result

Language

EN en language flag

Detected

N/A  language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brugge.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Brugge.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.

HTTPS certificate

SSL Certificate

Brugge.com has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Brugge.com is located in Europe, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Poor result

Social Sharing Optimization

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

brugge.com

Share this report in social media

Analyze another website

Analyze