8 sec in total
49 ms
5.5 sec
2.4 sec
Visit chathamwood.com now to see the best up-to-date Chatham Wood content and also check out these interesting facts you probably never knew about chathamwood.com
Rent at Chatham Wood Apartments Apartments in High Point , NC! These apartments are conveniently located near. Call us!
Visit chathamwood.comWe analyzed Chathamwood.com page load time and found that the first response time was 49 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
chathamwood.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value16.9 s
0/100
25%
Value23.2 s
0/100
10%
Value1,240 ms
19/100
30%
Value1.373
0/100
15%
Value17.0 s
4/100
10%
49 ms
15 ms
49 ms
59 ms
175 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 18% of them (20 requests) were addressed to the original Chathamwood.com, 35% (39 requests) were made to Cs-cdn.realpage.com and 13% (15 requests) were made to Capi.myleasestar.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source Cs-cdn.realpage.com.
Page size can be reduced by 917.0 kB (26%)
3.5 MB
2.6 MB
In fact, the total size of Chathamwood.com main page is 3.5 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. 75% 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.9 MB which makes up the majority of the site volume.
Potential reduce by 841.3 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 841.3 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. Chatham Wood images are well optimized though.
Potential reduce by 72.4 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 72.4 kB or 13% of the original size.
Potential reduce by 3.2 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. Chathamwood.com has all CSS files already compressed.
Number of requests can be reduced by 79 (80%)
99
20
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chatham 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 45 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.
chathamwood.com
49 ms
GetResource.ashx
15 ms
jquery.min.js
49 ms
jquery-ui.min.js
59 ms
global.min.js
175 ms
Accessibe.js
184 ms
font-awesome.min.css
186 ms
fontello.css
191 ms
bootstrap.min.css
210 ms
jquery.min.js
63 ms
jquery-ui.js
67 ms
jquery-migrate-1.4.1.js
47 ms
bootstrap.min.js
3345 ms
expanderPlugin.js
194 ms
lazy-line-painter-1.9.6.min.js
199 ms
jquery.fancybox.js
1504 ms
jquery.fancybox.min.js
240 ms
savannah.js
208 ms
doorway.min.js
56 ms
TweenMax.min.js
52 ms
ScrollMagic.min.js
63 ms
animation.gsap.js
70 ms
ScrollToPlugin.min.js
71 ms
sps-v3.js
239 ms
savannah-home.js
239 ms
slick.js
73 ms
slick.min.css
79 ms
slick-theme.min.css
72 ms
GetResource.ashx
28 ms
css-vars-ponyfill@1
46 ms
CommonData.js
39 ms
media-viewer.js
239 ms
GetResource.ashx
38 ms
GetResource.ashx
38 ms
flexslider.css
239 ms
jquery.mobile.toucheventsonly.min.js
239 ms
jquery.fancybox.css
239 ms
masonry.pkgd.min.js
3596 ms
slick.css
248 ms
slick.min.js
253 ms
datepicker.js
254 ms
cookies-consent.js
275 ms
GetResource.ashx
42 ms
WebResource.axd
43 ms
header.js
51 ms
jquery.flexslider-min.js
269 ms
hero.js
51 ms
footer.js
46 ms
ScriptResource.axd
52 ms
ScriptResource.axd
59 ms
loader.js
300 ms
OtAutoBlock.js
59 ms
otSDKStub.js
74 ms
css
53 ms
css
72 ms
gtm.js
133 ms
Y2PYZ-3WZ5U-9VEDC-WUEHY-8N7AV
114 ms
intersection-observer.js
490 ms
cssrelpreload.js
153 ms
151122696.png
1364 ms
151123069.png
451 ms
151123050.jpg
465 ms
151123063.jpg
784 ms
151123056.jpg
1893 ms
pattern.png
87 ms
151123054.jpg
697 ms
151123065.jpg
1195 ms
151123045.jpg
1872 ms
151123052.jpg
699 ms
151123048.jpg
701 ms
151123071.jpg
700 ms
151123055.jpg
1361 ms
151122696.png
702 ms
151123066.png
702 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3ig.ttf
67 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3ig.ttf
131 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3ig.ttf
215 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf
217 ms
QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf
217 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
217 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDXbtY.ttf
217 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
222 ms
fontello.woff
62 ms
fontello.woff
205 ms
fontawesome-webfont.woff
205 ms
rp-floorplans.cfd04e1d5e02d0ca83bd.js
245 ms
rp-floorplans.cfd04e1d5e02d0ca83bd.css
32 ms
config.json
338 ms
jquery-ui.css
23 ms
datepicker.css
150 ms
151123078.jpg
583 ms
d5b2c8d8-7fdf-4508-9c04-ded6229652e6.json
183 ms
GetResource.ashx
34 ms
jquery-ui.css
28 ms
font-awesome.min.css
162 ms
fontello.css
165 ms
bootstrap.min.css
177 ms
slick.min.css
161 ms
slick-theme.min.css
170 ms
GetResource.ashx
171 ms
jquery.fancybox.css
167 ms
GetResource.ashx
166 ms
GetResource.ashx
28 ms
flexslider.css
164 ms
slick.css
177 ms
datepicker.css
181 ms
GetResource.ashx
29 ms
rp-floorplans.cfd04e1d5e02d0ca83bd.css
180 ms
css
148 ms
css
183 ms
location
341 ms
datepicker.css
18 ms
chathamwood.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
Links do not have a discernible 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.
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
Some elements have a [tabindex] value greater than 0
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
chathamwood.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
Page has valid source maps
chathamwood.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
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 Chathamwood.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 Chathamwood.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.
chathamwood.com
Open Graph description is not detected on the main page of Chatham Wood. 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: