2.3 sec in total
113 ms
1.5 sec
705 ms
Visit 168plymouth.com now to see the best up-to-date 168 Plymouth content and also check out these interesting facts you probably never knew about 168plymouth.com
168 Plymouth features two iconic buildings connected by a private courtyard, offering 46 condos for sale including townhouses, lofts, and penthouses. Tour today.
Visit 168plymouth.comWe analyzed 168plymouth.com page load time and found that the first response time was 113 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
168plymouth.com performance score
name
value
score
weighting
Value1.8 s
91/100
10%
Value38.8 s
0/100
25%
Value9.1 s
14/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value13.4 s
11/100
10%
113 ms
23 ms
83 ms
41 ms
684 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 19% of them (12 requests) were addressed to the original 168plymouth.com, 63% (40 requests) were made to Images.ctfassets.net and 5% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (860 ms) relates to the external source Downloads.ctfassets.net.
Page size can be reduced by 1.5 MB (3%)
59.9 MB
58.3 MB
In fact, the total size of 168plymouth.com main page is 59.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. Only a small number of websites need less resources to load. Images take 59.8 MB which makes up the majority of the site volume.
Potential reduce by 64.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 10.6 kB, which is 13% 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 64.5 kB or 77% of the original size.
Potential reduce by 1.5 MB
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. 168 Plymouth images are well optimized though.
Potential reduce by 50 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 7 (12%)
59
52
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 168 Plymouth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
168plymouth.com
113 ms
modernizr.js
23 ms
site-c392416a5a5772ed3805.js
83 ms
style-c392416a5a5772ed3805.css
41 ms
gtm.js
684 ms
Herlo_for_website_intro.jpg
534 ms
jdv_IMG_1173.jpg
860 ms
dumbo-map.png
563 ms
168plymouth-elevation.svg
449 ms
equal-housing-opportunity.png
449 ms
1_-168_Plymouth_2.jpg
520 ms
Space_1.png
564 ms
Space_2.png
573 ms
Space_3-A.png
575 ms
SPACE_4_A.png
572 ms
Space_5.png
567 ms
Neighborhood_1.png
632 ms
Neighborhood_2.png
640 ms
168_Exterior_corner_3.jpg
634 ms
2-Entry.jpg
578 ms
Courtyard_for_website.png
645 ms
168_lobby.jpg
576 ms
Roffdeck_image_for_website.png
648 ms
4D_-_Brick_and_Timber_-_Main_space.jpg
635 ms
2_-_168_Plymouth_Corner_Living.jpg
636 ms
Brick___Timber_-__THA.png
745 ms
Building_5.png
651 ms
2_-_168_Plymouth_Corner_Living.jpg
640 ms
168_Plymouth_-_8C_-_living_room_view_of_Kitchen_and_dining.jpg
655 ms
168_Plymouth_-_8C_-_Living_Room_Northeast_Corner.jpg
645 ms
IMG_1053.jpg
646 ms
4D_-_Brick_and_Timber_-_Main_space.jpg
652 ms
168_Plymouth_-_3D_Bedroom_-_Field_Condition.jpg
651 ms
4D_-_Brick_and_Timber_-_Model_Detail.jpg
652 ms
4D_-_Brick_and_Timber_-_Primary_Bedroom_2.jpg
739 ms
4D_-_Brick_and_Timber_-_Living_2_-_crop.jpg
655 ms
THA_Entry_crop.jpg
657 ms
4b_-_Brick___Timber_-_A_THA.jpg
655 ms
GARDEN-CROP.jpg
748 ms
THC_-entry_crop.jpg
655 ms
Favorite_LIVING-3_-_sml.jpg
740 ms
PRIMARY_BEDROOM_copy_sml.jpg
738 ms
168_Plymouth-PHD-_Field_Condition.jpg
738 ms
168_Plymouth-PHC_Living_-_Field_Condition_-crop_sml.jpg
750 ms
PH-CROP.jpg
749 ms
icons.svg
392 ms
lineto-circular-pro-bold.woff
85 ms
37FD58_0_0.woff
127 ms
37FD58_1_0.woff
206 ms
37FD58_2_0.woff
145 ms
One_John.jpg
238 ms
Pearl.jpg
232 ms
185_Plymouth_St.jpg
186 ms
Water_Street.jpg
180 ms
js
137 ms
analytics.js
91 ms
71745.js
127 ms
fbevents.js
126 ms
collect
193 ms
collect
188 ms
collect
196 ms
collect
26 ms
js
93 ms
ga-audiences
45 ms
168plymouth.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-*] attributes do not match their roles
168plymouth.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
168plymouth.com SEO score
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 168plymouth.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 168plymouth.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.
168plymouth.com
Open Graph description is not detected on the main page of 168 Plymouth. 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: