4.7 sec in total
136 ms
4.1 sec
461 ms
Welcome to centraltower.ca homepage info - get ready to check Centraltower best content right away, or after learning these important things about centraltower.ca
Find luxury apartments for rent in Edmonton, Alberta by getting in touch with Central Tower. Pet-friendly, Eco-friendly. Book your private tour!
Visit centraltower.caWe analyzed Centraltower.ca page load time and found that the first response time was 136 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
centraltower.ca performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value20.6 s
0/100
25%
Value13.1 s
2/100
10%
Value2,680 ms
4/100
30%
Value0.155
74/100
15%
Value20.0 s
2/100
10%
136 ms
1356 ms
106 ms
810 ms
164 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 36% of them (24 requests) were addressed to the original Centraltower.ca, 57% (38 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Centraltower.ca.
Page size can be reduced by 1.6 MB (67%)
2.4 MB
812.4 kB
In fact, the total size of Centraltower.ca main page is 2.4 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. 80% 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. CSS take 940.1 kB which makes up the majority of the site volume.
Potential reduce by 155.7 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 155.7 kB or 87% of the original size.
Potential reduce by 3.1 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. Centraltower images are well optimized though.
Potential reduce by 628.6 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 628.6 kB or 73% of the original size.
Potential reduce by 843.4 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. Centraltower.ca needs all CSS files to be minified and compressed as it can save up to 843.4 kB or 90% of the original size.
Number of requests can be reduced by 20 (80%)
25
5
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Centraltower. 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 6 to 1 for CSS and as a result speed up the page load time.
centraltower.ca
136 ms
centraltower.ca
1356 ms
pum-site-styles.css
106 ms
style-static.min.css
810 ms
style.css
164 ms
js
63 ms
mediaelementplayer-legacy.min.css
115 ms
wp-mediaelement.min.css
115 ms
jquery.min.js
380 ms
jquery-migrate.min.js
164 ms
scripts.min.js
435 ms
bj-lazy-load.min.js
168 ms
core.min.js
168 ms
pum-site-scripts.js
273 ms
common.js
223 ms
mediaelement-and-player.min.js
383 ms
mediaelement-migrate.min.js
277 ms
wp-mediaelement.min.js
589 ms
jquery.fitvids.js
332 ms
motion-effects.js
602 ms
agent
159 ms
gtm.js
76 ms
fbevents.js
156 ms
logo-central-tower-new.png
270 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
222 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
426 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
479 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
481 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
480 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
523 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
524 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff
523 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
522 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff
523 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf
513 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff
554 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
555 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff
554 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
554 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff
555 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
553 ms
modules.ttf
220 ms
3.jpg
1303 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff
184 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
184 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff
184 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf
184 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff
182 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf
182 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff
187 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
187 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff
186 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
187 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff
274 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew-.ttf
273 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff
274 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew-.ttf
273 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff
274 ms
style.min.css
169 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw-.ttf
231 ms
DSC_7219EDM.jpg
218 ms
Screen-Shot-2020-02-05-at-1.04.47-PM.png
271 ms
centraltower.ca 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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
centraltower.ca 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
Browser errors were logged to the console
centraltower.ca 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
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 Centraltower.ca 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 Centraltower.ca 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.
centraltower.ca
Open Graph data is detected on the main page of Centraltower. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: