8.1 sec in total
412 ms
5.7 sec
1.9 sec
Visit neighbourly.com now to see the best up-to-date Neighbourly content for United Kingdom and also check out these interesting facts you probably never knew about neighbourly.com
An award-winning giving platform that connects company funds, surplus and volunteer time with local causes to make a positive impact.
Visit neighbourly.comWe analyzed Neighbourly.com page load time and found that the first response time was 412 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
neighbourly.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.2 s
11/100
25%
Value48.5 s
0/100
10%
Value93,410 ms
0/100
30%
Value0.094
91/100
15%
Value135.7 s
0/100
10%
412 ms
98 ms
141 ms
210 ms
324 ms
Our browser made a total of 159 requests to load all elements on the main page. We found that 9% of them (15 requests) were addressed to the original Neighbourly.com, 65% (104 requests) were made to Cdn2.neighbourly.com and 24% (38 requests) were made to Cdn1.neighbourly.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Cdn1.neighbourly.com.
Page size can be reduced by 324.9 kB (17%)
1.9 MB
1.5 MB
In fact, the total size of Neighbourly.com main page is 1.9 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 162.0 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 162.0 kB or 88% of the original size.
Potential reduce by 134.8 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. Neighbourly images are well optimized though.
Potential reduce by 26.5 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 26.5 kB or 15% of the original size.
Potential reduce by 1.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. Neighbourly.com has all CSS files already compressed.
Number of requests can be reduced by 63 (43%)
146
83
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neighbourly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.neighbourly.com
412 ms
nbrly-bundle.css
98 ms
nbrly-bs.css
141 ms
all.min.css
210 ms
nbrly-fonts.css
324 ms
main.737a4fbc.css
80 ms
require.js
322 ms
main.d85651cc.js
451 ms
config.js
89 ms
Montserrat-Regular.otf
627 ms
Montserrat-SemiBold.otf
87 ms
Montserrat-Light.otf
81 ms
Montserrat-Bold.otf
624 ms
Montserrat-ExtraBold.otf
623 ms
fa-solid-900.ttf
1008 ms
fa-regular-400.ttf
637 ms
fa-light-300.ttf
1435 ms
fa-thin-100.ttf
1619 ms
AppInsightsModule.js
24 ms
moment-with-locales.min.js
21 ms
toastr.min.js
18 ms
masonry.pkgd.min.js
47 ms
imagesloaded.pkgd.min.js
12 ms
getmyaccount
105 ms
js
192 ms
App.Path.Routes.Home
140 ms
nav-bar-dynamic.js
22 ms
home.js
22 ms
hype-animation.js
122 ms
composite-carousel.js
120 ms
global-stats-panel.js
116 ms
composite-feature-panel.js
117 ms
footer-cms.js
120 ms
contact-us.js
121 ms
gen_204
30 ms
branch-noun-util.js
39 ms
company-services.js
38 ms
image-url-builder.js
39 ms
menu-items.js
39 ms
text.js
41 ms
css.min.js
40 ms
toast-notifications.js
40 ms
i18n.js
23 ms
statistics-services.js
24 ms
number-utils.js
23 ms
currency-utils.js
24 ms
compositesearch-services.js
91 ms
social-utils.js
83 ms
jquery.inview.min.js
70 ms
slick.js
72 ms
nav-bar-dynamic.html
38 ms
home.html
40 ms
global-stats-panel.html
39 ms
composite-feature-panel.html
38 ms
composite-carousel.html
60 ms
hype-animation.html
54 ms
footer-cms.html
57 ms
contact-us.html
55 ms
nav-bar-dynamic.css
84 ms
composite-carousel.css
85 ms
hype-animation.css
88 ms
footer-cms.css
87 ms
contact-us.css
69 ms
resources.js
41 ms
resources.js
41 ms
resources.js
39 ms
resources.js
39 ms
resources.js
57 ms
resources.js
65 ms
resources.js
59 ms
resources.js
56 ms
resources.js
66 ms
resources.js
64 ms
resources.js
66 ms
system
222 ms
documents
407 ms
documents
370 ms
documents
806 ms
documents
799 ms
documents
409 ms
documents
470 ms
bcorp-68w@1x.png
286 ms
fr-68w@1x.png
285 ms
queens-award.png
286 ms
getmyaccount
658 ms
6182abe01d7fabc8cda6ffaa.jpg
423 ms
www.neighbourly.com
426 ms
nbrly-full-logo-blue.svg
55 ms
6182ab661d7fabc8cda6ffa8.png
2118 ms
6182ac0e1d7fabc8cda6ffac.jpg
430 ms
6182a9821d7fabc8cda6ff9d.png
505 ms
6182ac3bcc0f572cf075b8c2.jpg
506 ms
6182a924cc0f572cf075b8be.png
505 ms
6182ac57cc0f572cf075b8c4.jpg
508 ms
6182acf7cc0f572cf075b902.png
505 ms
60c89281e239e129779064a9.jpg
773 ms
6009eff3ee12353406dded73.jpg
775 ms
60c8b32be239e129779068d3.jpg
773 ms
600aeeecee12353406de20fa.jpg
771 ms
63161abd723a40577991e6f7.jpg
776 ms
62d7d0c6a914cfa5c8fa1eba.jpg
808 ms
62ecf6e4b51534573f3c9709.jpeg
776 ms
6332f594d82f89dc3cbf0390.jpg
815 ms
home-hero-desktop.js
46 ms
sidebar-nav-strip.js
51 ms
fa-brands-400.ttf
318 ms
base-animation-params.js
252 ms
sidebar-nav-strip.html
244 ms
sidebar-nav-strip.css
247 ms
resources.js
197 ms
ajax-loader.gif
126 ms
5e8af969c7ac8b0f38a10004.jpg
494 ms
5c658bf4c7ac862d50310ce5.jpg
496 ms
5edfb81fc7ac860bf48756c2.jpg
505 ms
5edfbecac7ac8b0b90024973.jpg
506 ms
5edfb494c7ac8b0b900247f1.png
525 ms
5dbc2616c7ac8b1f081c74eb.jpg
526 ms
5edfbf91c7ac8b0b900249a9.jpg
527 ms
5edfa7e4c7ac860bf48753de.jpg
528 ms
619cb707ca43d654f8d5ab9c.png
529 ms
6241ac6a3e3ffa5eaed8eb3c.jpg
530 ms
5edfc1e4c7ac860bf487584e.jpg
530 ms
59c3e7bcc7ac891f405f1207.jpeg
602 ms
621906f59f3b16ff12394e83.jpg
605 ms
60ab61497a2f860ef55616ef.png
1196 ms
59b68d2bc7ac89199c45c7dd.jpg
1199 ms
62fbacbb894b10409e57ff27.png
1261 ms
5ee7420cc7ac861a945ffa49.jpg
1340 ms
5edfb685c7ac860bf4875665.png
1398 ms
5edfbd27c7ac860bf4875789.jpg
1436 ms
5c53329ac7ac8b2fe0b1ba66.png
1401 ms
621755ea23521af0af0b67c0.png
1417 ms
App.Path.Routes.Home
578 ms
HYPE-598.thin.js
31 ms
nav-strip-item.js
22 ms
624425a89f046f083668c035.png
1330 ms
nav-strip-item.html
68 ms
park-done.svg
394 ms
volunteer.svg
426 ms
volunteering.svg
364 ms
sparkle.svg
435 ms
Moneybow.svg
422 ms
new-building-unfinished.svg
438 ms
new-building.svg
1093 ms
poundsign.svg
1027 ms
smoke.svg
1169 ms
truck-mask.svg
1171 ms
Truck-small.svg
1093 ms
Truck.svg
1230 ms
cars.svg
1265 ms
Surplus.svg
1270 ms
Land1.svg
1333 ms
town.svg
1336 ms
city1.svg
1366 ms
trees.svg
1387 ms
boat.svg
1365 ms
cloud1.svg
1389 ms
Fundraising.svg
1390 ms
Landscape-bg.svg
1428 ms
neighbourly.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
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.
neighbourly.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
neighbourly.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neighbourly.com 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 Neighbourly.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.
neighbourly.com
Open Graph data is detected on the main page of Neighbourly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: