Tools & Wizards About Us
wmplant.co.uk screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

wmplant.co.uk

Home - WM Plant | Construction Machinery Hire and Sales

Page Load Speed

11.1 sec in total

First Response

4 sec

Resources Loaded

6.6 sec

Page Rendered

530 ms

wmplant.co.uk screenshot

About Website

Click here to check amazing WM Plant content. Otherwise, check out these important facts you probably never knew about wmplant.co.uk

WM Plant provide hire, sales, spares, repairs and servicing of construction, horticultural and forestry machinery in Carlisle, Cumbria and Dumfries

Visit wmplant.co.uk

Key Findings

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

Performance Metrics

wmplant.co.uk performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value4,120 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value20.0 s

2/100

10%

Network Requests Diagram

wmplant.co.uk

3991 ms

style.min.css

165 ms

wc-blocks-vendors-style.css

241 ms

wc-blocks-style.css

318 ms

styles.css

244 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 77% of them (54 requests) were addressed to the original Wmplant.co.uk, 16% (11 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Wmplant.co.uk.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 174.3 kB

  • Original 219.0 kB
  • After minification 216.5 kB
  • After compression 44.7 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 174.3 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 4.2 kB

  • Original 624.6 kB
  • After minification 620.4 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. WM Plant images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 410.5 kB
  • After minification 410.5 kB
  • After compression 408.4 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

-8%

Potential reduce by 16.2 kB

  • Original 203.7 kB
  • After minification 203.5 kB
  • After compression 187.5 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. Wmplant.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (81%)

Requests Now

57

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wmplant.co.uk

wmplant.co.uk

3991 ms

style.min.css

style.min.css

165 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

241 ms

wc-blocks-style.css

wc-blocks-style.css

318 ms

styles.css

styles.css

244 ms

js_composer.min.css

js_composer.min.css

258 ms

css

css

25 ms

style.css

style.css

430 ms

style.css

style.css

249 ms

dynamic-styles-cached.css

dynamic-styles-cached.css

400 ms

jquery.min.js

jquery.min.js

412 ms

jquery-migrate.min.js

jquery-migrate.min.js

336 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

394 ms

add-to-cart.min.js

add-to-cart.min.js

404 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

417 ms

css

css

14 ms

css

css

12 ms

font-awesome.css

font-awesome.css

448 ms

hustle-icons.min.css

hustle-icons.min.css

448 ms

hustle-global.min.css

hustle-global.min.css

449 ms

hustle-info.min.css

hustle-info.min.css

450 ms

hustle-popup.min.css

hustle-popup.min.css

449 ms

rs6.css

rs6.css

450 ms

index.js

index.js

641 ms

index.js

index.js

641 ms

widget-product-wishlist.js

widget-product-wishlist.js

641 ms

widget-product-compare.js

widget-product-compare.js

641 ms

js_composer_front.min.js

js_composer_front.min.js

641 ms

rbtools.min.js

rbtools.min.js

791 ms

rs6.min.js

rs6.min.js

877 ms

js.cookie.min.js

js.cookie.min.js

718 ms

woocommerce.min.js

woocommerce.min.js

717 ms

cart-fragments.min.js

cart-fragments.min.js

718 ms

hustle-ui.min.js

hustle-ui.min.js

717 ms

underscore.min.js

underscore.min.js

811 ms

front.min.js

front.min.js

811 ms

imagesloaded.min.js

imagesloaded.min.js

810 ms

masonry.min.js

masonry.min.js

814 ms

api.js

api.js

55 ms

api.js

api.js

85 ms

jquery.masonry.min.js

jquery.masonry.min.js

841 ms

plugins-combined.js

plugins-combined.js

874 ms

controller.js

controller.js

728 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

727 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

721 ms

wp-polyfill.min.js

wp-polyfill.min.js

753 ms

index.js

index.js

742 ms

widget-product-search.js

widget-product-search.js

742 ms

widget-mailchimp.js

widget-mailchimp.js

732 ms

logo.png

logo.png

604 ms

arrow-select.svg

arrow-select.svg

616 ms

slider_pattern_white.png

slider_pattern_white.png

634 ms

dummy.png

dummy.png

632 ms

wmplany-logo-white.png

wmplany-logo-white.png

636 ms

slide1-1.jpg

slide1-1.jpg

927 ms

star.svg

star.svg

607 ms

quote.svg

quote.svg

663 ms

wm-plant-circular-saw-orange.jpg

wm-plant-circular-saw-orange.jpg

752 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmg.woff

191 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmg.woff

192 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyysd0mg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyysd0mg.woff

267 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmg.woff

301 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSysdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSysdUmg.woff

303 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2sdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiS2sdUmg.woff

304 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyusdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EVyusdUmg.woff

303 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EbiusdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1EbiusdUmg.woff

304 ms

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSusdUmg.woff

NGSpv5_NC0k9P_v6ZUCbLRAHxK1ECSusdUmg.woff

302 ms

font

font

301 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYw.woff

304 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

527 ms

Accessibility Review

wmplant.co.uk accessibility score

86

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

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wmplant.co.uk best practices score

92

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

SEO Factors

wmplant.co.uk SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UTF-8

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

wmplant.co.uk

Open Graph data is detected on the main page of WM Plant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: