6.7 sec in total
405 ms
5.4 sec
930 ms
Click here to check amazing Property Face content. Otherwise, check out these important facts you probably never knew about propertyface.com
Promote your listings with our endless marketing options: Social Media and Printable Designs, Lead Pages, Facebook Campaigns & many more!
Visit propertyface.comWe analyzed Propertyface.com page load time and found that the first response time was 405 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
propertyface.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.0 s
78/100
25%
Value4.3 s
75/100
10%
Value420 ms
65/100
30%
Value0.007
100/100
15%
Value3.7 s
90/100
10%
405 ms
231 ms
420 ms
262 ms
420 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that all of those requests were addressed to Propertyface.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Propertyface.com.
Page size can be reduced by 622.1 kB (75%)
827.5 kB
205.4 kB
In fact, the total size of Propertyface.com main page is 827.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 696.9 kB which makes up the majority of the site volume.
Potential reduce by 622.1 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 622.1 kB or 89% 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. Property Face images are well optimized though.
Number of requests can be reduced by 71 (81%)
88
17
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Property Face. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and as a result speed up the page load time.
propertyface.com
405 ms
f3IUQriTIMUUZOy9ysAWCKCNyDo.js
231 ms
jquery.min.js
420 ms
utils.min.js
262 ms
slick.min.js
420 ms
wp-polyfill-inert.min.js
361 ms
regenerator-runtime.min.js
362 ms
wp-polyfill.min.js
550 ms
index.js
459 ms
jquery.matchHeight-min.js
545 ms
matchHeight-init.js
579 ms
wpcf7r-fe.js
626 ms
hoverIntent.min.js
628 ms
hooks.min.js
671 ms
i18n.min.js
771 ms
common.min.js
771 ms
modernizr.js
802 ms
fusion-column-bg-image.js
846 ms
cssua.js
860 ms
fusion.js
894 ms
bootstrap.transition.js
986 ms
bootstrap.tooltip.js
988 ms
bootstrap.tab.js
1037 ms
jquery.waypoints.js
1068 ms
jquery.requestAnimationFrame.js
1083 ms
jquery.easing.js
1114 ms
jquery.fitvids.js
1199 ms
jquery.flexslider.js
1211 ms
jquery.hoverflow.js
1269 ms
jquery.hoverintent.js
1293 ms
jquery.ilightbox.js
1372 ms
jquery.mousewheel.js
1334 ms
jquery.placeholder.js
1414 ms
jquery.fade.js
1297 ms
fusion-equal-heights.js
1496 ms
fusion-parallax.js
1514 ms
fusion-video-general.js
1519 ms
fusion-video-bg.js
1341 ms
fusion-waypoints.js
1243 ms
fusion-lightbox.js
1076 ms
fusion-tooltip.js
1288 ms
fusion-sharing-box.js
1312 ms
jquery.sticky-kit.js
1325 ms
lazysizes.js
1079 ms
avada-skip-link-focus-fix.js
1224 ms
avada-general-footer.js
1236 ms
avada-quantity.js
1252 ms
avada-crossfade-images.js
1247 ms
avada-select.js
1323 ms
avada-tabs-widget.js
1288 ms
avada-contact-form-7.js
1085 ms
avada-live-search.js
1235 ms
fusion-alert.js
1122 ms
fusion-animations.js
1233 ms
fusion-menu.js
1233 ms
fusion-button.js
1250 ms
fusion-flexslider.js
1198 ms
jquery.textillate.js
1199 ms
fusion-title.js
1188 ms
fusion-tabs.js
1228 ms
fusion-container.js
1222 ms
avada-mobile-image-hover.js
1249 ms
avada-custom-header.js
1224 ms
avada-sidebars.js
1200 ms
bootstrap.scrollspy.js
1182 ms
avada-scrollspy.js
1224 ms
fusion-responsive-typography.js
1224 ms
fusion-scroll-to-anchor.js
1251 ms
fusion-general-global.js
1258 ms
fusion-vertical-menu-widget.js
1232 ms
fusion-video.js
1238 ms
fusion-column.js
1240 ms
lazyload.min.js
1226 ms
icomoon.woff
1358 ms
property-face-pack.ttf
1340 ms
new-logo250.png
1337 ms
homepage-hero-desktop_1.webp
1485 ms
homepage-hero-mobile-1.webp
1113 ms
Asset-22.png
1303 ms
test-roger.webp
1443 ms
call-center-man.png
1469 ms
NAR-badge.png
1333 ms
taradel-logo.png
1377 ms
avada-accountant-logo-@2x.png
1401 ms
douglas-logo.svg
1439 ms
remax-logo-1.svg
1423 ms
kw-logo-1.svg
438 ms
sothebys-logo-2.svg
658 ms
century21-logo.svg
660 ms
coldwell-logo-1.svg
693 ms
homepage-hero-desktop_1.webp
521 ms
propertyface.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
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
propertyface.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
propertyface.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 Propertyface.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 Propertyface.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.
propertyface.com
Open Graph data is detected on the main page of Property Face. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: