2.6 sec in total
147 ms
1.9 sec
562 ms
Click here to check amazing Watermark LIC content. Otherwise, check out these important facts you probably never knew about watermarklic.com
Watermark LIC’s studio, one, and two bedroom apartments provide all of the style and comfort you deserve. Experience the full spectrum of New York living from a colorful new perspective.
Visit watermarklic.comWe analyzed Watermarklic.com page load time and found that the first response time was 147 ms and then it took 2.4 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.
watermarklic.com performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value7.6 s
4/100
25%
Value3.9 s
82/100
10%
Value320 ms
76/100
30%
Value0
100/100
15%
Value6.1 s
63/100
10%
147 ms
802 ms
81 ms
164 ms
255 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 22% of them (14 requests) were addressed to the original Watermarklic.com, 47% (30 requests) were made to Fonts.gstatic.com and 8% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (917 ms) relates to the external source On-site.com.
Page size can be reduced by 120.8 kB (12%)
1.0 MB
894.6 kB
In fact, the total size of Watermarklic.com main page is 1.0 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. 65% of websites need less resources to load. Images take 547.7 kB which makes up the majority of the site volume.
Potential reduce by 57.6 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 9.3 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 57.6 kB or 77% of the original size.
Potential reduce by 7.3 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. Watermark LIC images are well optimized though.
Potential reduce by 54.7 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 54.7 kB or 17% of the original size.
Potential reduce by 1.1 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. Watermarklic.com has all CSS files already compressed.
Number of requests can be reduced by 18 (56%)
32
14
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watermark LIC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
watermarklic.com
147 ms
watermarklic.com
802 ms
gtm.js
81 ms
gtm.js
164 ms
js
255 ms
theme-3.css
215 ms
widget.min.js
491 ms
css
45 ms
scripts.min.js
341 ms
init-theme-3.js
332 ms
scripts.min.js
333 ms
popdown.min.js
332 ms
jquery-ui.css
179 ms
guest_card_contact_us.css
687 ms
jquery-ui.min.js
180 ms
257496.js
917 ms
otSDKStub.js
123 ms
234 ms
js
108 ms
201 ms
js
82 ms
analytics.js
167 ms
306 ms
213 ms
logo_sticky_1553109095.png
184 ms
logo_main_1554910082.svg
180 ms
1148_Watermark_9G_LR02_FINAL11-82e0964f941f44eb23259cb0c3e38451.jpg
342 ms
arrow-down.png
180 ms
collect
71 ms
rotator-gradient-top.png
163 ms
rotator-gradient-bottom.png
162 ms
pattern-bg.jpg
163 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrcVIT9d4cw.woff
61 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrcVIT9d4cydYA.woff
106 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCHPrcVIT9d4cydYA.woff
124 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCMPrcVIT9d4cydYA.woff
166 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCFPrcVIT9d4cydYA.woff
133 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrcVIT9d4cw.woff
134 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrcVIT9d4cydYA.woff
169 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCHPrcVIT9d4cydYA.woff
133 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCMPrcVIT9d4cydYA.woff
132 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCFPrcVIT9d4cydYA.woff
167 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrcVIT9d4cw.woff
168 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrcVIT9d4cydYA.woff
168 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCHPrcVIT9d4cydYA.woff
167 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCMPrcVIT9d4cydYA.woff
168 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCFPrcVIT9d4cydYA.woff
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrcVIT9d4cw.woff
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrcVIT9d4cydYA.woff
235 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCHPrcVIT9d4cydYA.woff
180 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCMPrcVIT9d4cydYA.woff
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCFPrcVIT9d4cydYA.woff
234 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrcVIT9d4cw.woff
173 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrcVIT9d4cydYA.woff
172 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCHPrcVIT9d4cydYA.woff
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCMPrcVIT9d4cydYA.woff
173 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCFPrcVIT9d4cydYA.woff
175 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrcVIT9d4cw.woff
175 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrcVIT9d4cydYA.woff
174 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCHPrcVIT9d4cydYA.woff
176 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCMPrcVIT9d4cydYA.woff
177 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCFPrcVIT9d4cydYA.woff
176 ms
collect
66 ms
ga-audiences
68 ms
watermarklic.com accessibility score
watermarklic.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
Missing source maps for large first-party JavaScript
watermarklic.com SEO score
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 Watermarklic.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 Watermarklic.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.
watermarklic.com
Open Graph data is detected on the main page of Watermark LIC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: