1.8 sec in total
197 ms
1.2 sec
372 ms
Welcome to projectline.ca homepage info - get ready to check Project Line best content right away, or after learning these important things about projectline.ca
ProjectLine helps small and mid-size companies maintain stability and drive growth using best-in-class ERP solutions, NetSuite and SAP Business One.
Visit projectline.caWe analyzed Projectline.ca page load time and found that the first response time was 197 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
projectline.ca performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value3.9 s
52/100
25%
Value3.3 s
90/100
10%
Value2,460 ms
4/100
30%
Value0.048
99/100
15%
Value12.8 s
13/100
10%
197 ms
190 ms
35 ms
198 ms
271 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 68% of them (39 requests) were addressed to the original Projectline.ca, 5% (3 requests) were made to Googletagmanager.com and 4% (2 requests) were made to No-cache.hubspot.com. The less responsive or slowest element that took the longest time to load (708 ms) belongs to the original domain Projectline.ca.
Page size can be reduced by 66.9 kB (12%)
561.9 kB
495.0 kB
In fact, the total size of Projectline.ca main page is 561.9 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. 50% of websites need less resources to load. Images take 396.3 kB which makes up the majority of the site volume.
Potential reduce by 56.9 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 12% 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 56.9 kB or 82% of the original size.
Potential reduce by 3.0 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. Project Line images are well optimized though.
Potential reduce by 6.2 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 660 B
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. Projectline.ca has all CSS files already compressed.
Number of requests can be reduced by 33 (59%)
56
23
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project Line. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.projectline.ca
197 ms
fjo6ijb.css
190 ms
module_57539361913_Main_Header.min.css
35 ms
module_57549638053_Hero_Two_Column.min.css
198 ms
module_61943007311_Three_Column.min.css
271 ms
slick.min.css
45 ms
module_57884390691_Testimonial_Slider.min.css
35 ms
module_57804382312_Tabber.css
55 ms
module_57532975739_Two_Column.min.css
275 ms
module_61911916323_Rich_Text.min.css
201 ms
module_57641533023_Main_Footer.min.css
70 ms
js
89 ms
js
141 ms
current.js
78 ms
jquery.min.js
91 ms
main.min.js
98 ms
jquery-1.11.2.js
118 ms
embed.js
52 ms
project.js
119 ms
module_57539361913_Main_Header.min.js
145 ms
project.js
147 ms
slick.min.js
385 ms
module_57884390691_Testimonial_Slider.min.js
165 ms
jquery.visible.min.js
193 ms
5273485.js
330 ms
index.js
245 ms
003cf88a12.js
65 ms
p.css
22 ms
AUiqImG1rBssg8Rb88hH
235 ms
gtm.js
114 ms
f995840c-609a-4595-aaa9-7c2b55ba4e8e.png
146 ms
Projecline%20Logo.png
277 ms
Scott-Delaney-Headshot-150x150.png
83 ms
Tom-Boehm-Headshot-150x150.png
82 ms
Sean-Lavin-Headshot-150x150.png
109 ms
Wholesale-Distribution-ERP-Solutions-600x300.jpg
109 ms
Manufacturing-600x300.jpg
276 ms
Industrial-Service-600x300.jpg
477 ms
Project-Planning-600x300.jpg
143 ms
SAP%20Logo.png
145 ms
netsuite-1.png
403 ms
logo-projectline-1.png
227 ms
linkedin-icon-2.png
405 ms
youtube-icon-1.png
708 ms
facebook-icon-2.png
556 ms
558ab3dc-506d-42b7-bb07-54e859d86112.png
231 ms
Symbol%205%20%E2%80%93%201.svg
152 ms
ProjectLine%20Background%20Accent%20%281%29.png
170 ms
hero-image-1%20%281%29.jpg
244 ms
green-quote.png
272 ms
footer-accent.svg
286 ms
hotjar-1497655.js
148 ms
web-interactives-embed.js
87 ms
leadflows.js
56 ms
5273485.js
88 ms
5273485.js
195 ms
fb.js
48 ms
projectline.ca accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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.
projectline.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
Page has valid source maps
projectline.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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Projectline.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 Projectline.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.
projectline.ca
Open Graph data is detected on the main page of Project Line. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: