11.6 sec in total
4.2 sec
7.2 sec
213 ms
Click here to check amazing Wholelife Project content. Otherwise, check out these important facts you probably never knew about wholelifeproject.co.uk
The Wholelife Project is a specialist rural skills company in North Devon
Visit wholelifeproject.co.ukWe analyzed Wholelifeproject.co.uk page load time and found that the first response time was 4.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
wholelifeproject.co.uk performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value6.4 s
9/100
25%
Value6.2 s
43/100
10%
Value180 ms
91/100
30%
Value0.913
3/100
15%
Value7.2 s
51/100
10%
4156 ms
319 ms
365 ms
232 ms
314 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 96% of them (67 requests) were addressed to the original Wholelifeproject.co.uk, 3% (2 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Wholelifeproject.co.uk.
Page size can be reduced by 1.5 MB (57%)
2.7 MB
1.2 MB
In fact, the total size of Wholelifeproject.co.uk main page is 2.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. 55% of websites need less resources to load. CSS take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.7 kB or 79% of the original size.
Potential reduce by 34.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. Wholelife Project images are well optimized though.
Potential reduce by 477.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 477.0 kB or 72% of the original size.
Potential reduce by 982.8 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. Wholelifeproject.co.uk needs all CSS files to be minified and compressed as it can save up to 982.8 kB or 88% of the original size.
Number of requests can be reduced by 50 (76%)
66
16
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wholelife Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.wholelifeproject.co.uk
4156 ms
wp-emoji-release.min.js
319 ms
dashicons.min.css
365 ms
jquery-ui-dialog.min.css
232 ms
settings.css
314 ms
css
24 ms
reset.css
222 ms
text.css
336 ms
960.css
342 ms
superfish.css
425 ms
prettyPhoto.css
426 ms
font-awesome.css
462 ms
style.css
653 ms
custom_style.css
472 ms
responsive.css
636 ms
js_composer.min.css
3748 ms
jquery.js
802 ms
jquery-migrate.min.js
580 ms
jquery.themepunch.tools.min.js
804 ms
jquery.themepunch.revolution.min.js
746 ms
prettyPhoto.css
120 ms
owl.carousel.css
135 ms
owl.theme.default.css
125 ms
animate.min.css
132 ms
core.min.js
243 ms
widget.min.js
240 ms
mouse.min.js
227 ms
resizable.min.js
230 ms
draggable.min.js
338 ms
button.min.js
332 ms
position.min.js
347 ms
dialog.min.js
338 ms
wpdialog.min.js
439 ms
jquery.prettyPhoto.js
457 ms
custom_params.js
462 ms
superfish.combined.js
464 ms
script.js
490 ms
jquery.meanmenu.min.js
555 ms
jquery.meanmenu.options.js
572 ms
wp-embed.min.js
568 ms
comment-reply.min.js
574 ms
js_composer_front.js
599 ms
jquery.prettyPhoto.js
670 ms
jquery.twbsPagination.min.js
688 ms
owl.carousel.js
787 ms
imagesloaded.pkgd.min.js
697 ms
underscore.min.js
698 ms
waypoints.min.js
779 ms
vc_grid_style_all.js
797 ms
vc_grid_style_load_more.js
807 ms
vc_grid_style_lazy.js
768 ms
vc_grid_style_pagination.js
861 ms
vc_grid.js
867 ms
Whole-Life-Logo.png
205 ms
slider32.jpg
622 ms
s1.jpg
204 ms
s4.jpg
231 ms
s5.jpg
226 ms
s6.jpg
619 ms
heading_underline.png
217 ms
sidebar-search.png
216 ms
double-arrow.png
288 ms
MG9KbUZFchDs94Tbv9U-pT8E0i7KZn-EPnyo3HZu7kw.woff
133 ms
fontawesome-webfont.woff
393 ms
wz1gqe57Mbg11v-OrLlVjj8E0i7KZn-EPnyo3HZu7kw.woff
132 ms
revolution.extension.carousel.min.js
188 ms
revolution.extension.navigation.min.js
202 ms
openhand.cur
103 ms
loader.gif
121 ms
revicons.woff
127 ms
wholelifeproject.co.uk 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
wholelifeproject.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wholelifeproject.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wholelifeproject.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 Wholelifeproject.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.
wholelifeproject.co.uk
Open Graph description is not detected on the main page of Wholelife Project. 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: