2.7 sec in total
245 ms
2.1 sec
416 ms
Click here to check amazing Oca content for Canada. Otherwise, check out these important facts you probably never knew about oca.ca
Visit oca.caWe analyzed Oca.ca page load time and found that the first response time was 245 ms and then it took 2.5 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.
oca.ca performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value15.7 s
0/100
25%
Value11.6 s
4/100
10%
Value200 ms
89/100
30%
Value0.042
99/100
15%
Value14.3 s
9/100
10%
245 ms
612 ms
268 ms
281 ms
208 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 47% of them (29 requests) were addressed to the original Oca.ca, 23% (14 requests) were made to Maps.googleapis.com and 11% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Oca.ca.
Page size can be reduced by 959.6 kB (38%)
2.5 MB
1.6 MB
In fact, the total size of Oca.ca main page is 2.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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 15.8 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 4.3 kB, which is 22% 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 15.8 kB or 81% of the original size.
Potential reduce by 18.8 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. Oca images are well optimized though.
Potential reduce by 743.9 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 743.9 kB or 70% of the original size.
Potential reduce by 181.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. Oca.ca needs all CSS files to be minified and compressed as it can save up to 181.2 kB or 87% of the original size.
Number of requests can be reduced by 24 (42%)
57
33
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oca. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
index.php
245 ms
ink-flex.min.css
612 ms
font-awesome.min.css
268 ms
oca.css
281 ms
modernizr.js
208 ms
holder.js
211 ms
ink-all.min.js
584 ms
autoload.js
286 ms
jquery-1.4.4.min.js
650 ms
toggle.js
383 ms
jquery.innerfade.js
364 ms
behaviours.js
366 ms
embed
231 ms
ico_menu.png
35 ms
BG_homepage.jpg
1017 ms
BG_grid01.jpg
90 ms
headerTop-logo_BG.png
417 ms
ico_home.png
101 ms
OCA_HL-Membership%20-%20Copy.jpg
123 ms
OCA_HL-Membership.jpg
232 ms
OCA_HL-Tenders.jpg
284 ms
OCA_HL-Tenders2.jpg
328 ms
cover.jpg
329 ms
icon_facebook.png
416 ms
icon_twitter.png
416 ms
logo-125Yrs.png
415 ms
logo_oycl_white.png
415 ms
bestbidz-newlogo.png
516 ms
logo_CCA.jpg
516 ms
Link2Build-Construction-Opportunity-Network.png
517 ms
js
87 ms
init_embed.js
41 ms
common.js
69 ms
map.js
89 ms
google4.png
41 ms
overlay.js
39 ms
util.js
112 ms
onion.js
111 ms
search_impl.js
113 ms
StaticMapService.GetMapImage
236 ms
stats.js
89 ms
openhand_8_8.cur
76 ms
ViewportInfoService.GetViewportInfo
46 ms
ViewportInfoService.GetViewportInfo
66 ms
kh
103 ms
transparent.png
33 ms
controls.js
29 ms
vt
76 ms
vt
145 ms
vt
147 ms
vt
146 ms
vt
147 ms
ViewportInfoService.GetViewportInfo
83 ms
css
102 ms
entity11.png
67 ms
mapcnt6.png
27 ms
tmapctrl.png
23 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
32 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
40 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
42 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
47 ms
AuthenticationService.Authenticate
27 ms
oca.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
Links do not have a discernible name
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
oca.ca 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
oca.ca 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oca.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 Oca.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.
oca.ca
Open Graph description is not detected on the main page of Oca. 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: