Tools & Wizards About Us
malmaison.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

malmaison.com

Discover Luxury Boutique Hotels & Dining | Malmaison

Page Load Speed

4.7 sec in total

First Response

170 ms

Resources Loaded

3.5 sec

Page Rendered

1 sec

malmaison.com screenshot

About Website

Welcome to malmaison.com homepage info - get ready to check Malmaison best content for United Kingdom right away, or after learning these important things about malmaison.com

Explore boutique hotels with a difference at Malmaison. Uniquely designed rooms, renowned restaurants, spas & more in prime locations.

Visit malmaison.com

Key Findings

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

Performance Metrics

malmaison.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value4,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value46.6 s

0/100

10%

Network Requests Diagram

malmaison.com

170 ms

malmaison.com

277 ms

www.malmaison.com

334 ms

polyfill.min.js

77 ms

aspnet-validation.min.js

308 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 57% of them (35 requests) were addressed to the original Malmaison.com, 11% (7 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source App.vouchconcierge.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 137.6 kB (21%)

Content Size

669.4 kB

After Optimization

531.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Malmaison.com main page is 669.4 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. 70% of websites need less resources to load. Javascripts take 568.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 55.2 kB

  • Original 68.9 kB
  • After minification 54.4 kB
  • After compression 13.6 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 14.5 kB, which is 21% 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 55.2 kB or 80% of the original size.

JavaScript Optimization

-13%

Potential reduce by 73.0 kB

  • Original 568.0 kB
  • After minification 568.0 kB
  • After compression 495.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 73.0 kB or 13% of the original size.

CSS Optimization

-29%

Potential reduce by 9.3 kB

  • Original 32.6 kB
  • After minification 32.6 kB
  • After compression 23.3 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. Malmaison.com needs all CSS files to be minified and compressed as it can save up to 9.3 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (36%)

Requests Now

47

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

malmaison.com

malmaison.com

170 ms

malmaison.com

malmaison.com

277 ms

www.malmaison.com

www.malmaison.com

334 ms

polyfill.min.js

polyfill.min.js

77 ms

aspnet-validation.min.js

aspnet-validation.min.js

308 ms

mal.css

mal.css

376 ms

runtime.bundle.js

runtime.bundle.js

307 ms

vendor.bundle.js

vendor.bundle.js

623 ms

app.bundle.js

app.bundle.js

395 ms

quickbook.bundle.js

quickbook.bundle.js

157 ms

css2

css2

34 ms

gtm.js

gtm.js

148 ms

olq6xdx.js

olq6xdx.js

203 ms

mallogo.svg

mallogo.svg

203 ms

homepage-hero-pattern.svg

homepage-hero-pattern.svg

186 ms

malmaison-manchester-deansgate-public-areas-4.jpg

malmaison-manchester-deansgate-public-areas-4.jpg

354 ms

h2-blob.svg

h2-blob.svg

184 ms

winter-sale-1.jpg

winter-sale-1.jpg

424 ms

malmaison-bar-grill-mains-4.jpg

malmaison-bar-grill-mains-4.jpg

373 ms

workplusplay-food-for-thought-menu-1.jpg

workplusplay-food-for-thought-menu-1.jpg

367 ms

mal-reading-wplusp-2-private-dining-4-jan-24-hero-shot.jpg

mal-reading-wplusp-2-private-dining-4-jan-24-hero-shot.jpg

355 ms

mal-york-weddings-2.webp

mal-york-weddings-2.webp

356 ms

malmaison-bar-grill-cocktails-3.jpg

malmaison-bar-grill-cocktails-3.jpg

367 ms

blob-2.svg

blob-2.svg

366 ms

club-deluxe-room-2.jpg

club-deluxe-room-2.jpg

396 ms

mal-manchester-restaurant-1.webp

mal-manchester-restaurant-1.webp

507 ms

52131258896_9517fa0a6c_k.jpg

52131258896_9517fa0a6c_k.jpg

447 ms

mal-liverpool-signature-suite-8.webp

mal-liverpool-signature-suite-8.webp

438 ms

mal-aberdeen-grill-1-1.webp

mal-aberdeen-grill-1-1.webp

522 ms

york-club-twin-room-1.jpg

york-club-twin-room-1.jpg

481 ms

mal-edinburgh-city-bar-2.webp

mal-edinburgh-city-bar-2.webp

561 ms

home.svg

home.svg

511 ms

blob-3.svg

blob-3.svg

513 ms

banner-blob.svg

banner-blob.svg

549 ms

sign-up-footer-image.webp

sign-up-footer-image.webp

591 ms

mal_web_logo_lock_up-01.svg

mal_web_logo_lock_up-01.svg

598 ms

ai.2.min.js

ai.2.min.js

114 ms

92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJQVG.ttf

26 ms

92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7myRJQVG.ttf

51 ms

92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mz9JQVG.ttf

114 ms

92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mx9IgVG.ttf

114 ms

92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf

92zPtBhPNqw79Ij1E865zBUv7mxEIgVG.ttf

112 ms

icomoon.ttf

icomoon.ttf

519 ms

font.woff

font.woff

536 ms

92zJtBhPNqw73oHH7BbQp4-B6XlrZu0FNI0.ttf

92zJtBhPNqw73oHH7BbQp4-B6XlrZu0FNI0.ttf

113 ms

92zJtBhPNqw73oHH7BbQp4-B6XlrZgoCNI0.ttf

92zJtBhPNqw73oHH7BbQp4-B6XlrZgoCNI0.ttf

114 ms

bat.js

bat.js

142 ms

ld7tjgkrri

ld7tjgkrri

222 ms

otSDKStub.js

otSDKStub.js

173 ms

15337780.js

15337780.js

11 ms

15337780

15337780

41 ms

4c985b6d-5f06-40d7-8778-5121008b87dc.json

4c985b6d-5f06-40d7-8778-5121008b87dc.json

174 ms

clarity.js

clarity.js

8 ms

location

location

49 ms

otBannerSdk.js

otBannerSdk.js

35 ms

app.js

app.js

1039 ms

app.css

app.css

986 ms

d

d

16 ms

d

d

42 ms

p.gif

p.gif

45 ms

c.gif

c.gif

7 ms

Accessibility Review

malmaison.com accessibility score

98

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

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

Best Practices

malmaison.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

malmaison.com SEO score

86

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

malmaison.com

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