Tools & Wizards About Us
carpetnextday.co.uk screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

carpetnextday.co.uk

Home - Carpet Next Day

Page Load Speed

3.4 sec in total

First Response

182 ms

Resources Loaded

2.8 sec

Page Rendered

427 ms

carpetnextday.co.uk screenshot

About Website

Visit carpetnextday.co.uk now to see the best up-to-date Carpet Next Day content and also check out these interesting facts you probably never knew about carpetnextday.co.uk

Visit carpetnextday.co.uk

Key Findings

We analyzed Carpetnextday.co.uk page load time and found that the first response time was 182 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

carpetnextday.co.uk performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

carpetnextday.co.uk

182 ms

www.carpetnextday.co.uk

179 ms

www.carpetnextday.co.uk

395 ms

style.min.css

345 ms

style.css

398 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 96% of them (82 requests) were addressed to the original Carpetnextday.co.uk, 1% (1 request) were made to Stats.wp.com and 1% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Carpetnextday.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.0 kB (13%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Carpetnextday.co.uk main page is 1.3 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. 50% of websites need less resources to load. Images take 548.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 157.9 kB

  • Original 191.5 kB
  • After minification 182.6 kB
  • After compression 33.5 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 157.9 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 548.0 kB
  • After minification 548.0 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. Carpet Next Day images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.6 kB

  • Original 505.3 kB
  • After minification 505.3 kB
  • After compression 501.6 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

-7%

Potential reduce by 7.5 kB

  • Original 101.5 kB
  • After minification 101.5 kB
  • After compression 94.1 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. Carpetnextday.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (89%)

Requests Now

74

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

carpetnextday.co.uk

carpetnextday.co.uk

182 ms

www.carpetnextday.co.uk

www.carpetnextday.co.uk

179 ms

www.carpetnextday.co.uk

www.carpetnextday.co.uk

395 ms

style.min.css

style.min.css

345 ms

style.css

style.css

398 ms

gdpr-main-nf.css

gdpr-main-nf.css

342 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

337 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

353 ms

wp-polyfill.min.js

wp-polyfill.min.js

57 ms

hooks.min.js

hooks.min.js

67 ms

w.js

w.js

15 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

79 ms

jquery-migrate-3.1.0.min.js

jquery-migrate-3.1.0.min.js

98 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

111 ms

add-to-cart.min.js

add-to-cart.min.js

124 ms

js.cookie.min.js

js.cookie.min.js

137 ms

woocommerce.min.js

woocommerce.min.js

155 ms

wc-quantity-increment.min.js

wc-quantity-increment.min.js

169 ms

number-polyfill.min.js

number-polyfill.min.js

183 ms

wc-blocks.css

wc-blocks.css

172 ms

dashicons.min.css

dashicons.min.css

189 ms

display-structure.css

display-structure.css

201 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

217 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

226 ms

sourcebuster.min.js

sourcebuster.min.js

244 ms

order-attribution.min.js

order-attribution.min.js

257 ms

react.min.js

react.min.js

270 ms

deprecated.min.js

deprecated.min.js

282 ms

dom.min.js

dom.min.js

294 ms

react-dom.min.js

react-dom.min.js

323 ms

escape-html.min.js

escape-html.min.js

324 ms

element.min.js

element.min.js

643 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

696 ms

i18n.min.js

i18n.min.js

334 ms

keycodes.min.js

keycodes.min.js

650 ms

priority-queue.min.js

priority-queue.min.js

657 ms

compose.min.js

compose.min.js

350 ms

private-apis.min.js

private-apis.min.js

366 ms

redux-routine.min.js

redux-routine.min.js

434 ms

js

js

62 ms

data.min.js

data.min.js

690 ms

lodash.min.js

lodash.min.js

404 ms

wc-blocks-registry.js

wc-blocks-registry.js

480 ms

url.min.js

url.min.js

468 ms

api-fetch.min.js

api-fetch.min.js

449 ms

wc-settings.js

wc-settings.js

436 ms

data-controls.min.js

data-controls.min.js

425 ms

html-entities.min.js

html-entities.min.js

412 ms

notices.min.js

notices.min.js

394 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

380 ms

wc-blocks-data.js

wc-blocks-data.js

390 ms

dom-ready.min.js

dom-ready.min.js

379 ms

a11y.min.js

a11y.min.js

367 ms

primitives.min.js

primitives.min.js

366 ms

warning.min.js

warning.min.js

361 ms

blocks-components.js

blocks-components.js

362 ms

blocks-checkout.js

blocks-checkout.js

356 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

357 ms

plugins.min.js

plugins.min.js

355 ms

script.min.js

script.min.js

356 ms

script-later.min.js

script-later.min.js

355 ms

main.js

main.js

675 ms

underscore.min.js

underscore.min.js

345 ms

backbone.min.js

backbone.min.js

662 ms

front-end-deps.js

front-end-deps.js

675 ms

front-end.js

front-end.js

347 ms

search.min.js

search.min.js

357 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

359 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

369 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

355 ms

g.gif

g.gif

128 ms

vimeo.min.js

vimeo.min.js

601 ms

placeholder.svg

placeholder.svg

284 ms

SofiaProSemiBold.woff

SofiaProSemiBold.woff

652 ms

SofiaProRegular.woff

SofiaProRegular.woff

596 ms

carpet-next-day-logo.svg

carpet-next-day-logo.svg

499 ms

carpet-next-day-dark-logo.svg

carpet-next-day-dark-logo.svg

795 ms

fa-solid-900.woff

fa-solid-900.woff

1008 ms

fa-regular-400.woff

fa-regular-400.woff

1045 ms

fa-light-300.woff

fa-light-300.woff

1084 ms

SofiaProBold.woff

SofiaProBold.woff

931 ms

SofiaProExtraLight.woff

SofiaProExtraLight.woff

613 ms

fa-brands-400.woff

fa-brands-400.woff

1076 ms

Maidstone-scaled-e1665144617130.jpg

Maidstone-scaled-e1665144617130.jpg

934 ms

mejs-controls.svg

mejs-controls.svg

397 ms

Accessibility Review

carpetnextday.co.uk accessibility score

95

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

Heading elements are not in a sequentially-descending order

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

carpetnextday.co.uk best practices score

83

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

Page has valid source maps

SEO Factors

carpetnextday.co.uk SEO score

91

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

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carpetnextday.co.uk 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 Carpetnextday.co.uk main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

carpetnextday.co.uk

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