3.3 sec in total
454 ms
2.5 sec
318 ms
Click here to check amazing John D Wood content. Otherwise, check out these important facts you probably never knew about johndwood.com
We are an all-inclusive commercial property consultancy providing professional services across the property market, including investment, management, and agency.
Visit johndwood.comWe analyzed Johndwood.com page load time and found that the first response time was 454 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
johndwood.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value16.4 s
0/100
25%
Value10.8 s
6/100
10%
Value1,260 ms
19/100
30%
Value0.002
100/100
15%
Value15.6 s
6/100
10%
454 ms
200 ms
234 ms
201 ms
203 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 85% of them (94 requests) were addressed to the original Johndwood.com, 14% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (720 ms) belongs to the original domain Johndwood.com.
Page size can be reduced by 998.3 kB (42%)
2.4 MB
1.4 MB
In fact, the total size of Johndwood.com main page is 2.4 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. 60% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 137.9 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 137.9 kB or 83% of the original size.
Potential reduce by 0 B
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. John D Wood images are well optimized though.
Potential reduce by 351.9 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 351.9 kB or 23% of the original size.
Potential reduce by 508.4 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. Johndwood.com needs all CSS files to be minified and compressed as it can save up to 508.4 kB or 77% of the original size.
Number of requests can be reduced by 90 (96%)
94
4
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John D Wood. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 70 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
johndwood.com
454 ms
qr-code-generator.css
200 ms
team.min.css
234 ms
frontend.min.css
201 ms
swiper.min.css
203 ms
e-swiper.min.css
207 ms
post-6.css
208 ms
widget-spacer.min.css
262 ms
widget-heading.min.css
263 ms
shapes.min.css
274 ms
fadeIn.min.css
275 ms
widget-text-editor.min.css
276 ms
widget-call-to-action.min.css
296 ms
transitions.min.css
321 ms
post-16519.css
342 ms
houzez-studio-public.css
343 ms
ht-qrcode.css
343 ms
all-css.css
525 ms
all.min.css
360 ms
style.css
379 ms
css
32 ms
script.min.js
359 ms
jquery.min.js
413 ms
jquery-migrate.min.js
373 ms
houzez-studio-public.js
368 ms
rs6.css
443 ms
lazysizes.min.js
425 ms
react.min.js
427 ms
react-dom.min.js
594 ms
react-jsx-runtime.min.js
590 ms
dom-ready.min.js
591 ms
hooks.min.js
591 ms
i18n.min.js
591 ms
a11y.min.js
593 ms
wp-polyfill.min.js
593 ms
url.min.js
594 ms
api-fetch.min.js
594 ms
css
18 ms
blob.min.js
543 ms
block-serialization-default-parser.min.js
472 ms
autop.min.js
470 ms
deprecated.min.js
481 ms
dom.min.js
465 ms
escape-html.min.js
495 ms
element.min.js
463 ms
is-shallow-equal.min.js
502 ms
keycodes.min.js
499 ms
priority-queue.min.js
489 ms
compose.min.js
489 ms
private-apis.min.js
494 ms
redux-routine.min.js
469 ms
data.min.js
473 ms
html-entities.min.js
453 ms
rich-text.min.js
465 ms
shortcode.min.js
462 ms
warning.min.js
458 ms
blocks.min.js
513 ms
moment.min.js
443 ms
date.min.js
497 ms
primitives.min.js
446 ms
components.min.js
588 ms
keyboard-shortcuts.min.js
407 ms
commands.min.js
441 ms
notices.min.js
449 ms
preferences-persistence.min.js
300 ms
preferences.min.js
312 ms
style-engine.min.js
337 ms
token-list.min.js
335 ms
wordcount.min.js
364 ms
block-editor.min.js
554 ms
qr-code-generator.js
387 ms
team.min.js
402 ms
easy.qrcode.min.js
409 ms
qrcode-custom.js
422 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8JoA.woff
22 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8JoA.woff
49 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8JoA.woff
62 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8JoA.woff
62 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff
63 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8JoA.woff
63 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8JoA.woff
63 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8JoA.woff
60 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8JoA.woff
64 ms
KFOmCnqEu92Fr1Mu4mxM.woff
63 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
65 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
64 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
64 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
65 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
65 ms
core.min.js
454 ms
jquery.form.min.js
448 ms
rbtools.min.js
470 ms
rs6.min.js
531 ms
all-scripts.js
498 ms
houzez-instant-page.js
479 ms
menu.min.js
480 ms
autocomplete.min.js
720 ms
mouse.min.js
719 ms
slider.min.js
719 ms
jquery.vide.min.js
719 ms
custom.min.js
715 ms
property-carousels.min.js
715 ms
webpack-pro.runtime.min.js
690 ms
webpack.runtime.min.js
689 ms
frontend-modules.min.js
679 ms
frontend.min.js
677 ms
frontend.min.js
665 ms
elements-handlers.min.js
631 ms
houzez-iconfont.ttf
615 ms
lazyloader-1.gif
601 ms
bg-marker-right-1.jpg
588 ms
johndwood.com accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
johndwood.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
johndwood.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
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 Johndwood.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 Johndwood.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.
johndwood.com
Open Graph data is detected on the main page of John D Wood. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: