2.3 sec in total
164 ms
1.6 sec
490 ms
Click here to check amazing HMS content. Otherwise, check out these important facts you probably never knew about hms.ca
Experts in enterprise timesheet and project management systems and publishers of TimeControl, timesheet software for the entire organization.
Visit hms.caWe analyzed Hms.ca page load time and found that the first response time was 164 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
hms.ca performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value13.4 s
0/100
25%
Value6.1 s
45/100
10%
Value920 ms
30/100
30%
Value0.095
91/100
15%
Value11.0 s
21/100
10%
164 ms
474 ms
68 ms
26 ms
161 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 54% of them (37 requests) were addressed to the original Hms.ca, 26% (18 requests) were made to Platform.twitter.com and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (814 ms) belongs to the original domain Hms.ca.
Page size can be reduced by 49.3 kB (2%)
2.7 MB
2.6 MB
In fact, the total size of Hms.ca main page is 2.7 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. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 27.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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 20% 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 27.0 kB or 78% of the original size.
Potential reduce by 9.6 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. HMS images are well optimized though.
Potential reduce by 876 B
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 11.8 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. Hms.ca needs all CSS files to be minified and compressed as it can save up to 11.8 kB or 46% of the original size.
Number of requests can be reduced by 20 (34%)
59
39
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
hms.ca
164 ms
www.hms.ca
474 ms
js
68 ms
css
26 ms
main-min.1429727334.css
161 ms
app-min.js
384 ms
tc_logo.png
453 ms
tci_logo.png
452 ms
hms-logo-small.png
236 ms
hms-logo.png
237 ms
gunnison_300x144.png
237 ms
opalrt_logo_300x117.jpg
453 ms
whp_engineering_300x124.jpg
319 ms
hamondeltak_300x137.jpg
453 ms
otonabee.jpg
619 ms
marchconsulting.png
483 ms
aedon_consulting.png
483 ms
valuerecovery.png
555 ms
e2pm.png
483 ms
asl_environmental.png
483 ms
acr-systems.png
636 ms
esi_tennessee.png
563 ms
mds-sciex.png
561 ms
ftservices.png
561 ms
rolls-royce.png
634 ms
transcontinental-printing.png
639 ms
highlands_county.png
639 ms
scisyslogo.png
640 ms
ascendant.png
702 ms
parker-hannifin.png
758 ms
nuscale.png
758 ms
murray_roberts.png
758 ms
widgets.js
17 ms
hms_bg.png
814 ms
hms-logo-white.png
588 ms
close.png
616 ms
loading.gif
629 ms
prev.png
629 ms
next.png
630 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
9 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
16 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
17 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
36 ms
fontawesome-webfont.woff
484 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
35 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
35 ms
analytics.js
43 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
36 ms
settings
104 ms
collect
13 ms
js
50 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
4 ms
HMS_TimeControl
60 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
12 ms
runtime-b1c52fd0a13ead5fcf6b.js
42 ms
modules-96ebc7ac3ad66d681a3d.js
49 ms
main-babd9234dc048fb47339.js
44 ms
_app-a9c9f1a99e4414675fb1.js
71 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
74 ms
_buildManifest.js
83 ms
_ssgManifest.js
83 ms
8526.0c32a8f0cfc5749221a3.js
22 ms
1755.07a49c40b12af4f75780.js
21 ms
8283.f3e5048cca7cef5eed7f.js
22 ms
3077.44bfeb00af01bc4020f6.js
23 ms
1362.42d432e02f7980bca032.js
22 ms
4956.c4e51ef593974b9db0bb.js
24 ms
5893.d500bd2a89ded806aa73.js
21 ms
hms.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
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.
hms.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
Issues were logged in the Issues panel in Chrome Devtools
hms.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
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 Hms.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 Hms.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.
hms.ca
Open Graph data is detected on the main page of HMS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: