Tools & Wizards About Us
why-bother.co.uk screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

why-bother.co.uk

Cleaners Brighton | Cleaning Services Brighton & Hove - Why Bother

Page Load Speed

2 sec in total

First Response

355 ms

Resources Loaded

1.2 sec

Page Rendered

414 ms

why-bother.co.uk screenshot

About Website

Welcome to why-bother.co.uk homepage info - get ready to check Why Bother best content right away, or after learning these important things about why-bother.co.uk

We are a cleaning company in Brighton, specialising in both office cleaning and domestic cleaning, the number one choice for cleaning services in Brighton.

Visit why-bother.co.uk

Key Findings

We analyzed Why-bother.co.uk page load time and found that the first response time was 355 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

why-bother.co.uk performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

why-bother.co.uk

355 ms

www.why-bother.co.uk

311 ms

301182418.js

35 ms

1080143649.js

51 ms

animate.min.css

43 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that all of those requests were addressed to Why-bother.co.uk and no external sources were called. The less responsive or slowest element that took the longest time to load (399 ms) belongs to the original domain Why-bother.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.1 kB (17%)

Content Size

938.8 kB

After Optimization

774.7 kB

  • HTML
  • Images

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

HTML Optimization

-79%

Potential reduce by 164.1 kB

  • Original 206.8 kB
  • After minification 202.9 kB
  • After compression 42.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 164.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 732.0 kB
  • After minification 732.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. Why Bother images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 40 (69%)

Requests Now

58

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

why-bother.co.uk

why-bother.co.uk

355 ms

www.why-bother.co.uk

www.why-bother.co.uk

311 ms

301182418.js

301182418.js

35 ms

1080143649.js

1080143649.js

51 ms

animate.min.css

animate.min.css

43 ms

style.min.css

style.min.css

44 ms

theme.min.css

theme.min.css

67 ms

header-footer.min.css

header-footer.min.css

68 ms

frontend-lite.min.css

frontend-lite.min.css

73 ms

swiper.min.css

swiper.min.css

86 ms

post-2783.css

post-2783.css

71 ms

frontend-lite.min.css

frontend-lite.min.css

79 ms

post-41.css

post-41.css

105 ms

post-2786.css

post-2786.css

100 ms

post-2863.css

post-2863.css

108 ms

style.css

style.css

112 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

116 ms

logo.svg

logo.svg

112 ms

animations.min.css

animations.min.css

178 ms

post-4719.css

post-4719.css

134 ms

post-4821.css

post-4821.css

140 ms

1357142857.js

1357142857.js

141 ms

dom-ready.min.js

dom-ready.min.js

169 ms

hooks.min.js

hooks.min.js

144 ms

i18n.min.js

i18n.min.js

176 ms

a11y.min.js

a11y.min.js

166 ms

jquery.min.js

jquery.min.js

172 ms

jquery.json.min.js

jquery.json.min.js

196 ms

gravityforms.min.js

gravityforms.min.js

203 ms

conditional_logic.min.js

conditional_logic.min.js

204 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

202 ms

utils.min.js

utils.min.js

224 ms

vendor-theme.min.js

vendor-theme.min.js

212 ms

scripts-theme.min.js

scripts-theme.min.js

237 ms

app.js

app.js

317 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

231 ms

app.js

app.js

319 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

318 ms

webpack.runtime.min.js

webpack.runtime.min.js

294 ms

frontend-modules.min.js

frontend-modules.min.js

283 ms

frontend.min.js

frontend.min.js

284 ms

waypoints.min.js

waypoints.min.js

280 ms

core.min.js

core.min.js

260 ms

frontend.min.js

frontend.min.js

260 ms

elements-handlers.min.js

elements-handlers.min.js

259 ms

WBC-Header-Image-Edited-Compressed-1536x1024.jpg

WBC-Header-Image-Edited-Compressed-1536x1024.jpg

270 ms

nastuh-abootalebi-yWwob8kwOCk-unsplash-150x150.jpg

nastuh-abootalebi-yWwob8kwOCk-unsplash-150x150.jpg

376 ms

sidekix-media-iQYdCr4EpE-unsplash-150x150.jpg

sidekix-media-iQYdCr4EpE-unsplash-150x150.jpg

331 ms

christopher-jolly-GqbU78bdJFM-unsplash-150x150.jpg

christopher-jolly-GqbU78bdJFM-unsplash-150x150.jpg

349 ms

jakub-zerdzicki-z0xdapnPMJ8-unsplash-1-150x150.jpg

jakub-zerdzicki-z0xdapnPMJ8-unsplash-1-150x150.jpg

242 ms

dane-deaner-_-KLkj7on_c-unsplash-2-768x523.jpg

dane-deaner-_-KLkj7on_c-unsplash-2-768x523.jpg

251 ms

christian-mackie-6BJu73-UJpg-unsplash-1024x697.jpg

christian-mackie-6BJu73-UJpg-unsplash-1024x697.jpg

247 ms

samantha-gades-BlIhVfXbi9s-unsplash-768x768.jpg

samantha-gades-BlIhVfXbi9s-unsplash-768x768.jpg

246 ms

minh-pham-OtXADkUh3-I-unsplash-768x768.jpg

minh-pham-OtXADkUh3-I-unsplash-768x768.jpg

244 ms

trustist-logo-new-compressed.svg

trustist-logo-new-compressed.svg

251 ms

IMG_1729-768x768.jpg

IMG_1729-768x768.jpg

399 ms

hamish-duncan-BiL6PyJPuk8-unsplash-1024x295.jpg

hamish-duncan-BiL6PyJPuk8-unsplash-1024x295.jpg

365 ms

80562778_126334138849663_4209870912742222168_n.jpg

80562778_126334138849663_4209870912742222168_n.jpg

316 ms

brighton-silhouette.png

brighton-silhouette.png

339 ms

why-bother-icon-1.svg

why-bother-icon-1.svg

311 ms

roboto-400.woff

roboto-400.woff

139 ms

roboto-500.woff

roboto-500.woff

148 ms

roboto-300.woff

roboto-300.woff

175 ms

Accessibility Review

why-bother.co.uk accessibility score

98

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.

Best Practices

why-bother.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

High

Page has valid source maps

SEO Factors

why-bother.co.uk SEO score

93

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 doesn't use 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 Why-bother.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 Why-bother.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

why-bother.co.uk

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