2.8 sec in total
206 ms
2.5 sec
147 ms
Click here to check amazing Property Swim content. Otherwise, check out these important facts you probably never knew about propertyswim.com
The annual JLL Property Triathlon is back in 2026 for its 19th edition, proudly supporting our charity partner Age UK.
Visit propertyswim.comWe analyzed Propertyswim.com page load time and found that the first response time was 206 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
propertyswim.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value11.2 s
0/100
25%
Value8.3 s
19/100
10%
Value3,030 ms
2/100
30%
Value0.066
97/100
15%
Value15.7 s
6/100
10%
206 ms
187 ms
528 ms
55 ms
37 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Propertyswim.com, 79% (41 requests) were made to Propertytriathlon.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (928 ms) relates to the external source Propertytriathlon.com.
Page size can be reduced by 801.7 kB (72%)
1.1 MB
312.9 kB
In fact, the total size of Propertyswim.com main page is 1.1 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. CSS take 714.9 kB which makes up the majority of the site volume.
Potential reduce by 84.5 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 11.3 kB, which is 11% 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 84.5 kB or 83% of the original size.
Potential reduce by 2.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. Property Swim images are well optimized though.
Potential reduce by 128.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 128.5 kB or 54% of the original size.
Potential reduce by 585.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. Propertyswim.com needs all CSS files to be minified and compressed as it can save up to 585.8 kB or 82% of the original size.
Number of requests can be reduced by 33 (77%)
43
10
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Property Swim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
propertyswim.com
206 ms
www.propertyswim.com
187 ms
www.propertytriathlon.com
528 ms
Bootstrap.js
55 ms
font-awesome.min.css
37 ms
css2
42 ms
style.min.css
743 ms
bbpress.min.css
488 ms
styles.css
510 ms
cookie-law-info-public.css
417 ms
cookie-law-info-gdpr.css
738 ms
wpa-style.css
474 ms
bootstrap.min.css
819 ms
jquery.fancybox.css
613 ms
main.css
651 ms
style.css
842 ms
js_composer.min.css
627 ms
jquery.min.js
645 ms
jquery-migrate.min.js
649 ms
cookie-law-info-public.js
798 ms
isotope.pkgd.min.js
815 ms
main.js
747 ms
fancybox.js
750 ms
countdown.js
759 ms
fingerprint.min.js
762 ms
livevalidation_standalone.compressed.js
30 ms
cookie-law-info-table.css
766 ms
wp-polyfill-inert.min.js
773 ms
regenerator-runtime.min.js
776 ms
wp-polyfill.min.js
783 ms
hooks.min.js
785 ms
i18n.min.js
927 ms
index.js
928 ms
index.js
804 ms
longdesc.min.js
818 ms
wp-accessibility.min.js
822 ms
js_composer_front.min.js
870 ms
logo2025.png
30 ms
jll-logo-white.svg
95 ms
mail.svg
30 ms
eg.png
31 ms
WWF_Logo_RGB.png
58 ms
twitter.svg
59 ms
gtm.js
98 ms
index.html
452 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf
68 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf
122 ms
fa-regular-400.woff
621 ms
fa-light-300.woff
429 ms
fa-solid-900.woff
477 ms
solar3.png
251 ms
fontawesome-webfont.woff
73 ms
propertyswim.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
Image elements do not have [alt] attributes
Links do not have a discernible name
propertyswim.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
propertyswim.com 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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Propertyswim.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 Propertyswim.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.
propertyswim.com
Open Graph data is detected on the main page of Property Swim. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: