5.1 sec in total
1.1 sec
3.6 sec
431 ms
Visit cutting-hedge.com now to see the best up-to-date Cutting Hedge content and also check out these interesting facts you probably never knew about cutting-hedge.com
London landscape gardeners, Cutting Hedge™ provide reliable garden landscaping and maintenance services across South West London including Ealing, Chiswick and Richmond
Visit cutting-hedge.comWe analyzed Cutting-hedge.com page load time and found that the first response time was 1.1 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cutting-hedge.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value50.4 s
0/100
25%
Value33.8 s
0/100
10%
Value5,560 ms
0/100
30%
Value0.18
67/100
15%
Value35.4 s
0/100
10%
1099 ms
70 ms
142 ms
138 ms
139 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 96% of them (47 requests) were addressed to the original Cutting-hedge.com, 2% (1 request) were made to Netdna.bootstrapcdn.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Cutting-hedge.com.
Page size can be reduced by 411.1 kB (7%)
5.7 MB
5.3 MB
In fact, the total size of Cutting-hedge.com main page is 5.7 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 5.4 MB which makes up the majority of the site volume.
Potential reduce by 21.4 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 3.7 kB, which is 14% 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 21.4 kB or 79% of the original size.
Potential reduce by 173.7 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. Cutting Hedge images are well optimized though.
Potential reduce by 78.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 78.0 kB or 56% of the original size.
Potential reduce by 138.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. Cutting-hedge.com needs all CSS files to be minified and compressed as it can save up to 138.0 kB or 84% of the original size.
Number of requests can be reduced by 27 (56%)
48
21
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cutting Hedge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cutting-hedge.com
1099 ms
normalize.min.css
70 ms
style.css
142 ms
styles.css
138 ms
cff-style.css
139 ms
font-awesome.min.css
7 ms
jquery.fancybox.css
169 ms
camera.css
165 ms
public.css
131 ms
wps-fbre-front.css
205 ms
jquery.min.js
28 ms
jquery.fancybox.js
203 ms
jquery.easing.js
201 ms
jquery.form.min.js
239 ms
scripts.js
240 ms
cff-scripts.js
237 ms
wp-embed.min.js
266 ms
responsiveslides.min.js
267 ms
main.js
272 ms
wp-emoji-release.min.js
119 ms
bg.jpg
1197 ms
menu.png
148 ms
call.png
149 ms
body-bg.png
150 ms
1.jpg
537 ms
2.jpg
475 ms
3.jpg
582 ms
4.jpg
599 ms
61.jpg
661 ms
51.jpg
730 ms
7.jpg
733 ms
cuttinghedgeGroup.png
651 ms
gm.png
915 ms
ag.png
906 ms
gd.png
916 ms
ig.png
2227 ms
fb-icon.png
1611 ms
gp-icon.png
1609 ms
mail.png
1608 ms
call.png
1612 ms
to-top.png
1610 ms
fancy_shadow_n.png
1637 ms
fancy_shadow_ne.png
1634 ms
fancy_shadow_e.png
1636 ms
fancy_shadow_se.png
1633 ms
fancy_shadow_s.png
1635 ms
fancy_shadow_sw.png
1715 ms
fancy_shadow_w.png
1711 ms
fancy_shadow_nw.png
1718 ms
cutting-hedge.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
cutting-hedge.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
cutting-hedge.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cutting-hedge.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Cutting-hedge.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.
cutting-hedge.com
Open Graph description is not detected on the main page of Cutting Hedge. 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: