Tools & Wizards About Us
mariner.london screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

mariner.london

Mariner London - High End, Luxury Furniture & Furnishings Since 1893

Page Load Speed

11.7 sec in total

First Response

481 ms

Resources Loaded

10.1 sec

Page Rendered

1.1 sec

mariner.london screenshot

About Website

Welcome to mariner.london homepage info - get ready to check Mariner best content right away, or after learning these important things about mariner.london

125 Years Of Crafting High End, Exclusive, Luxury Furniture & Lighting. Prestigious Interior Design and Luxury Furnishings.

Visit mariner.london

Key Findings

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

Performance Metrics

mariner.london performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value41.2 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value3,200 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.462

19/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

www.mariner.london

481 ms

style.min.css

323 ms

jquery.min.js

1236 ms

jquery-migrate.min.js

384 ms

css

31 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 51% of them (43 requests) were addressed to the original Mariner.london, 15% (13 requests) were made to Embed.tawk.to and 7% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Mariner.london.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (10%)

Content Size

10.1 MB

After Optimization

9.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mariner.london main page is 10.1 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 9.5 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.7 kB

  • Original 61.1 kB
  • After minification 57.4 kB
  • After compression 10.3 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 50.7 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 936.2 kB

  • Original 9.5 MB
  • After minification 8.5 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. Mariner images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 29.6 kB

  • Original 445.9 kB
  • After minification 445.9 kB
  • After compression 416.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 3.5 kB

  • Original 107.5 kB
  • After minification 107.5 kB
  • After compression 104.0 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. Mariner.london has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (53%)

Requests Now

77

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.mariner.london

www.mariner.london

481 ms

style.min.css

style.min.css

323 ms

jquery.min.js

jquery.min.js

1236 ms

jquery-migrate.min.js

jquery-migrate.min.js

384 ms

css

css

31 ms

css

css

42 ms

css

css

48 ms

css

css

54 ms

fontawesome.css

fontawesome.css

1445 ms

bootstrap.css

bootstrap.css

28 ms

featherlight.css

featherlight.css

38 ms

featherlight.gallery.css

featherlight.gallery.css

48 ms

slick.css

slick.css

75 ms

slick-theme.css

slick-theme.css

85 ms

style.css

style.css

96 ms

jquery.js

jquery.js

1436 ms

modernizr.js

modernizr.js

105 ms

bootstrap.js

bootstrap.js

116 ms

slick.min.js

slick.min.js

1429 ms

featherlight.min.js

featherlight.min.js

59 ms

main.js

main.js

1540 ms

featherlight.min.js

featherlight.min.js

12 ms

css

css

17 ms

css

css

14 ms

analytics.js

analytics.js

115 ms

1.1.HP_1.jpg

1.1.HP_1.jpg

1909 ms

6rD3k5OmEGc

6rD3k5OmEGc

233 ms

logo1.png

logo1.png

1315 ms

001.jpeg

001.jpeg

1233 ms

002.jpeg

002.jpeg

1132 ms

003-792x1024.jpeg

003-792x1024.jpeg

1039 ms

004.jpeg

004.jpeg

1664 ms

005.jpeg

005.jpeg

1449 ms

006-768x1024.jpeg

006-768x1024.jpeg

2279 ms

007.jpeg

007.jpeg

2424 ms

008.jpeg

008.jpeg

2397 ms

009.jpeg

009.jpeg

2393 ms

010.jpeg

010.jpeg

2406 ms

011.jpeg

011.jpeg

2456 ms

012.jpeg

012.jpeg

2965 ms

013.jpeg

013.jpeg

3005 ms

014.jpeg

014.jpeg

3193 ms

015-776x1024.jpeg

015-776x1024.jpeg

3269 ms

016.jpeg

016.jpeg

3385 ms

017.jpeg

017.jpeg

3389 ms

018.jpeg

018.jpeg

3532 ms

019.jpeg

019.jpeg

3726 ms

020.jpeg

020.jpeg

5233 ms

021.jpeg

021.jpeg

5213 ms

022.jpeg

022.jpeg

5168 ms

023.jpeg

023.jpeg

5243 ms

024.jpeg

024.jpeg

6389 ms

1.2.HP_2.jpg

1.2.HP_2.jpg

2520 ms

default

default

152 ms

ajax-loader.gif.html

ajax-loader.gif.html

4813 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

57 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

68 ms

fontawesome-webfont-v=4.7.0.woff

fontawesome-webfont-v=4.7.0.woff

7075 ms

collect

collect

27 ms

js

js

51 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

52 ms

ad_status.js

ad_status.js

186 ms

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

QIgJXlTW_ocH5BKR4VvT459F7KnrK51w4wqraUAmDYI.js

124 ms

embed.js

embed.js

36 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

32 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

39 ms

id

id

21 ms

Create

Create

100 ms

GenerateIT

GenerateIT

13 ms

log_event

log_event

15 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

53 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

202 ms

twk-event-polyfill.js

twk-event-polyfill.js

194 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

72 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

69 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

171 ms

twk-main.js

twk-main.js

62 ms

twk-vendor.js

twk-vendor.js

75 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

232 ms

twk-chunk-common.js

twk-chunk-common.js

83 ms

twk-runtime.js

twk-runtime.js

93 ms

twk-app.js

twk-app.js

96 ms

Accessibility Review

mariner.london accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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

mariner.london best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mariner.london 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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

mariner.london

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