3.4 sec in total
9 ms
3 sec
427 ms
Visit citymark.com now to see the best up-to-date Citymark content and also check out these interesting facts you probably never knew about citymark.com
We build community.
Visit citymark.comWe analyzed Citymark.com page load time and found that the first response time was 9 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
citymark.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value7.2 s
5/100
25%
Value11.5 s
5/100
10%
Value1,330 ms
17/100
30%
Value1.738
0/100
15%
Value18.6 s
3/100
10%
9 ms
2237 ms
75 ms
318 ms
489 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 88% of them (57 requests) were addressed to the original Citymark.com, 8% (5 requests) were made to Unpkg.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Citymark.com.
Page size can be reduced by 202.7 kB (57%)
352.5 kB
149.8 kB
In fact, the total size of Citymark.com main page is 352.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. 65% of websites need less resources to load. CSS take 145.9 kB which makes up the majority of the site volume.
Potential reduce by 62.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 8.4 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 62.6 kB or 81% of the original size.
Potential reduce by 127 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. Citymark images are well optimized though.
Potential reduce by 28.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 28.4 kB or 25% of the original size.
Potential reduce by 111.5 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. Citymark.com needs all CSS files to be minified and compressed as it can save up to 111.5 kB or 76% of the original size.
Number of requests can be reduced by 34 (61%)
56
22
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citymark. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
citymark.com
9 ms
citymark.com
2237 ms
js
75 ms
style.min.css
318 ms
styles.css
489 ms
ww.css
244 ms
style.css
240 ms
swiper-bundle.css
265 ms
plyr.css
240 ms
cookieBar.css
151 ms
screen.css
233 ms
print.css
173 ms
style.css
254 ms
frontend-gtag.min.js
261 ms
jquery.min.js
332 ms
swiper-bundle.min.js
400 ms
jquery.cookieBar.js
331 ms
jquery.countTo.js
330 ms
plyr@3
200 ms
ajax_app.js
341 ms
hero-image-carousel.css
412 ms
classic-block.css
412 ms
parallax-block.css
412 ms
video-block.css
482 ms
image-text-repeater-block.css
546 ms
index.js
553 ms
index.js
561 ms
common.js
550 ms
theme.js
556 ms
hero-image-carousel.js
558 ms
parallax-block.js
582 ms
video-block.js
583 ms
swiper-bundle.css
17 ms
plyr@3
15 ms
plyr.min.js
21 ms
citymark_logo_white-svg-1.png
276 ms
menu-hamburger.svg
76 ms
citymark_logo_white.svg
78 ms
close.svg
79 ms
slider-2@2x-1-scaled-1-1920x995.webp
81 ms
slider-2@2x-1-scaled-1-640x490.webp
83 ms
slider-1@2x-1-scaled-1-1920x995.webp
83 ms
slider-1@2x-1-scaled-1-640x490.webp
84 ms
348_Celsius_CityMark.webp
88 ms
348_Celsius_CityMark-640x490.webp
83 ms
6X8A9388-copy-scaled-4.webp
86 ms
6X8A9388-copy-scaled-4-640x490.webp
84 ms
citymark-mark-white@2x.png
86 ms
Gallery-by-CityMark-01-e1653902636903.webp
87 ms
bcg-development@2x-935x795.webp
88 ms
bcg-realty@2x-935x795.webp
89 ms
christin-hume-Hcfwew744z4-unsplash-2-935x795.webp
89 ms
contact-us-1-3-935x795.webp
90 ms
bcg-life-starts@2x-935x795.webp
90 ms
citymark-mark-white-footer-n.png
90 ms
Equal-Housing-Opportunity-Logo-300x270-300x270-1.png
91 ms
citymark-mark-white.svg
95 ms
swiper-arrow.svg
91 ms
select-arrow.svg
93 ms
triangle.png
31 ms
citymark-logo-vertical-white.svg
31 ms
FuturaCyrillicLight.woff
9 ms
FuturaCyrillicBook.woff
10 ms
FuturaCyrillicMedium.woff
10 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
8 ms
citymark.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
citymark.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
citymark.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 Citymark.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 Citymark.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.
citymark.com
Open Graph data is detected on the main page of Citymark. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: