Tools & Wizards About Us
terminusmontparnasse.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

terminusmontparnasse.com

Hôtel Terminus Montparnasse | Site Officiel | Paris

Page Load Speed

2.9 sec in total

First Response

354 ms

Resources Loaded

2.2 sec

Page Rendered

355 ms

terminusmontparnasse.com screenshot

About Website

Welcome to terminusmontparnasse.com homepage info - get ready to check Terminus Montparnasse best content right away, or after learning these important things about terminusmontparnasse.com

The Hôtel Terminus Montparnasse, ideally located in front of Montparnasse Station and in close proximity to the Saint-Germain district, welcomes you to its official website.

Visit terminusmontparnasse.com

Key Findings

We analyzed Terminusmontparnasse.com page load time and found that the first response time was 354 ms and then it took 2.5 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

terminusmontparnasse.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

terminusmontparnasse.com

354 ms

www.terminusmontparnasse.com

599 ms

prototype.js

235 ms

swfobject.js

153 ms

script.js

154 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 442.9 kB (53%)

Content Size

834.2 kB

After Optimization

391.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Terminusmontparnasse.com main page is 834.2 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. Javascripts take 485.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.3 kB

  • Original 21.4 kB
  • After minification 19.3 kB
  • After compression 5.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. 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 16.3 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 16.1 kB

  • Original 279.7 kB
  • After minification 263.6 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. Terminus Montparnasse images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 371.3 kB

  • Original 485.0 kB
  • After minification 395.1 kB
  • After compression 113.7 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 371.3 kB or 77% of the original size.

CSS Optimization

-81%

Potential reduce by 39.2 kB

  • Original 48.1 kB
  • After minification 36.3 kB
  • After compression 8.9 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. Terminusmontparnasse.com needs all CSS files to be minified and compressed as it can save up to 39.2 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (54%)

Requests Now

57

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

terminusmontparnasse.com

terminusmontparnasse.com

354 ms

www.terminusmontparnasse.com

www.terminusmontparnasse.com

599 ms

prototype.js

prototype.js

235 ms

swfobject.js

swfobject.js

153 ms

script.js

script.js

154 ms

lytebox.js

lytebox.js

155 ms

swf-charte.jsa

swf-charte.jsa

165 ms

scriptaculous.js

scriptaculous.js

158 ms

ideptool_infobulle.js

ideptool_infobulle.js

230 ms

ideptool_menu.js

ideptool_menu.js

230 ms

jscal2.css

jscal2.css

230 ms

border-radius.css

border-radius.css

255 ms

jscal2.js

jscal2.js

256 ms

fr.js

fr.js

304 ms

jquery.min.js

jquery.min.js

460 ms

styles.css

styles.css

308 ms

charte.css

charte.css

312 ms

lytebox.css

lytebox.css

316 ms

integration.css

integration.css

380 ms

texteLong1.css

texteLong1.css

381 ms

texteLongImageCourte2.css

texteLongImageCourte2.css

380 ms

texteMoyenTexteMoyen1.css

texteMoyenTexteMoyen1.css

386 ms

encart-icons.css

encart-icons.css

388 ms

yepnope.php

yepnope.php

452 ms

encartnoFlash-wcb.css

encartnoFlash-wcb.css

452 ms

encart-coordonnees.css

encart-coordonnees.css

455 ms

builder.js

builder.js

218 ms

effects.js

effects.js

220 ms

dragdrop.js

dragdrop.js

283 ms

controls.js

controls.js

286 ms

slider.js

slider.js

287 ms

sound.js

sound.js

288 ms

awstats_misc_tracker.js

awstats_misc_tracker.js

91 ms

bg-body.jpg

bg-body.jpg

457 ms

bg-container.png

bg-container.png

91 ms

bg-header.png

bg-header.png

79 ms

logo.png

logo.png

77 ms

pict-contact.png

pict-contact.png

79 ms

pict-plan.png

pict-plan.png

154 ms

pict-prox.png

pict-prox.png

156 ms

1pop-84.jpg

1pop-84.jpg

157 ms

disney.png

disney.png

229 ms

f_logo.png

f_logo.png

230 ms

logo-handicap.png

logo-handicap.png

234 ms

logo_adh_10_fr_s.png

logo_adh_10_fr_s.png

236 ms

GroupeLinkeo.png

GroupeLinkeo.png

251 ms

trajanpro-bold-webfont.woff

trajanpro-bold-webfont.woff

366 ms

styles.css

styles.css

290 ms

framebox.js.php

framebox.js.php

341 ms

canvasloader.php

canvasloader.php

340 ms

ideoslider.core.php

ideoslider.core.php

393 ms

btnPrevMiniature.png

btnPrevMiniature.png

77 ms

btnNextMiniature.png

btnNextMiniature.png

78 ms

bg-menuTop.png

bg-menuTop.png

105 ms

pic.png

pic.png

218 ms

puce.png

puce.png

153 ms

bg-wcb.png

bg-wcb.png

154 ms

picto-phone.png

picto-phone.png

154 ms

encart-milieuCoor.png

encart-milieuCoor.png

177 ms

puceCoor.png

puceCoor.png

179 ms

bg-containerfooter.jpg

bg-containerfooter.jpg

228 ms

bg-footer.png

bg-footer.png

242 ms

btn_up.png

btn_up.png

232 ms

framebox.js.php

framebox.js.php

261 ms

Accessibility Review

terminusmontparnasse.com accessibility score

89

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

Links do not have a discernible name

Best Practices

terminusmontparnasse.com 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

terminusmontparnasse.com SEO score

97

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    FR

  • Encoding

    UTF-8

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

Social Sharing Optimization

terminusmontparnasse.com

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