3.6 sec in total
171 ms
3.1 sec
393 ms
Visit primestaff.ca now to see the best up-to-date Prime Staff content and also check out these interesting facts you probably never knew about primestaff.ca
Visit primestaff.caWe analyzed Primestaff.ca page load time and found that the first response time was 171 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
primestaff.ca performance score
name
value
score
weighting
Value5.8 s
5/100
10%
Value10.5 s
0/100
25%
Value9.5 s
12/100
10%
Value1,260 ms
19/100
30%
Value0.099
90/100
15%
Value14.1 s
10/100
10%
171 ms
1400 ms
99 ms
43 ms
155 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 83% of them (96 requests) were addressed to the original Primestaff.ca, 8% (9 requests) were made to Fonts.gstatic.com and 4% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Primestaff.ca.
Page size can be reduced by 300.5 kB (17%)
1.8 MB
1.5 MB
In fact, the total size of Primestaff.ca main page is 1.8 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. 75% 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. Javascripts take 979.7 kB which makes up the majority of the site volume.
Potential reduce by 204.0 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 204.0 kB or 83% of the original size.
Potential reduce by 4.9 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. Prime Staff images are well optimized though.
Potential reduce by 62.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 28.7 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. Primestaff.ca has all CSS files already compressed.
Number of requests can be reduced by 92 (92%)
100
8
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prime Staff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 51 to 1 for CSS and as a result speed up the page load time.
primestaff.ca
171 ms
primestaff.ca
1400 ms
wp-emoji-release.min.js
99 ms
css
43 ms
style.min.css
155 ms
wc-blocks-vendors-style.css
168 ms
wc-blocks-style.css
226 ms
classic-themes.min.css
169 ms
jquerysctipttop.css
49 ms
chat-font-style.css
171 ms
style.css
172 ms
style.min.css
208 ms
style.min.css
220 ms
style.css
222 ms
elementor-icons.min.css
238 ms
frontend-lite.min.css
282 ms
post-11.css
262 ms
frontend-lite.min.css
275 ms
global.css
277 ms
js_composer.min.css
340 ms
jquery-ui.css
288 ms
flaticon.css
316 ms
font-awesome.css
329 ms
selectize.default.css
332 ms
mapbox-gl.css
41 ms
mapbox-gl-geocoder.css
38 ms
mapbox-gl-directions.css
41 ms
intlTelInput.css
334 ms
plugin.css
398 ms
plugin-responsive.css
370 ms
patch.css
382 ms
jquery.datetimepicker.css
385 ms
jquery.tagit.css
387 ms
fancybox.css
392 ms
slick-slider.css
425 ms
mediaelementplayer.css
436 ms
careerfy-styles.css
439 ms
elementer-style.css
442 ms
bootstrap.css
449 ms
font-awesome.min.css
459 ms
woocommerce.css
480 ms
style.css
610 ms
css
42 ms
css
45 ms
pusher.min.js
34 ms
wp-jobsearch-plugin.css
528 ms
css
13 ms
common-detail.css
404 ms
responsive.css
354 ms
jobsearch-floating-window-styles.css
348 ms
jobsearch-chat-style.css
375 ms
custom-styles.css
386 ms
animate.min.css
400 ms
rs6.css
369 ms
jquery.min.js
378 ms
jquery-migrate.min.js
389 ms
language-cookie.js
427 ms
jquery.blockUI.min.js
426 ms
add-to-cart.min.js
405 ms
woocommerce-add-to-cart.js
392 ms
zxcvbn-async.min.js
388 ms
jquery-ui.js
505 ms
careerfy-elementor.js
398 ms
jquery.nicescroll.min.js
362 ms
jobsearch-chat-functions.js
356 ms
rbtools.min.js
432 ms
rs6.min.js
524 ms
js.cookie.min.js
377 ms
woocommerce.min.js
367 ms
regenerator-runtime.min.js
358 ms
wp-polyfill.min.js
401 ms
hooks.min.js
468 ms
i18n.min.js
464 ms
css
13 ms
password-strength-meter.min.js
449 ms
login-registration.js
434 ms
selectize.min.js
422 ms
fitvideo.js
420 ms
jobsearch-plugin.js
417 ms
jobsearch-common.js
423 ms
fancybox.pack.js
429 ms
isotope.min.js
513 ms
moment.min.js
500 ms
jquery.datetimepicker.full.min.js
490 ms
slick-slider.js
488 ms
careerfy-common.js
462 ms
smush-lazy-load.min.js
449 ms
bootstrap.js
523 ms
functions.js
520 ms
jobsearch-floating-window-script.js
514 ms
js_composer_front.min.js
501 ms
vc-waypoints.min.js
488 ms
skrollr.min.js
437 ms
counter.js
436 ms
intlTelInput.js
437 ms
dummy.png
278 ms
service-pattren-bg.png
305 ms
trending-category-bgfull.png
249 ms
pxiEyp8kv8JHgFVrJJfed3FHGPc.ttf
27 ms
pxiByp8kv8JHgFVrLGT9Z1xlEN2JQEk.ttf
138 ms
pxiByp8kv8JHgFVrLDz8Z1xlEN2JQEk.ttf
139 ms
pxiByp8kv8JHgFVrLFj_Z1xlEN2JQEk.ttf
142 ms
pxiGyp8kv8JHgFVrLPTucHtFOvWDSA.ttf
141 ms
pxiByp8kv8JHgFVrLEj6Z1xlEN2JQEk.ttf
141 ms
pxiByp8kv8JHgFVrLCz7Z1xlEN2JQEk.ttf
139 ms
pxiByp8kv8JHgFVrLDD4Z1xlEN2JQEk.ttf
141 ms
pxiByp8kv8JHgFVrLBT5Z1xlEN2JQEk.ttf
140 ms
fontawesome-webfont.woff
242 ms
fontawesome-webfont.woff
387 ms
careerfy.ttf
335 ms
icomoon.ttf
194 ms
Sans-titre-1.png
73 ms
fr.png
74 ms
zxcvbn.min.js
206 ms
counter-nine-bgfull2.jpg
78 ms
primestaff.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.
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
primestaff.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
Missing source maps for large first-party JavaScript
primestaff.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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primestaff.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Primestaff.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.
primestaff.ca
Open Graph description is not detected on the main page of Prime Staff. 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: