2.5 sec in total
513 ms
1.8 sec
228 ms
Click here to check amazing Inkline content. Otherwise, check out these important facts you probably never knew about inkline.ca
Solutions that convert. We are a full service Ottawa web design agency, providing creative and digital services, all focused on delivering results.
Visit inkline.caWe analyzed Inkline.ca page load time and found that the first response time was 513 ms and then it took 2 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.
inkline.ca performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value12.1 s
0/100
25%
Value8.5 s
18/100
10%
Value690 ms
43/100
30%
Value0.706
7/100
15%
Value12.3 s
15/100
10%
513 ms
242 ms
137 ms
147 ms
130 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 54% of them (33 requests) were addressed to the original Inkline.ca, 43% (26 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Cdn.iubenda.com. The less responsive or slowest element that took the longest time to load (667 ms) belongs to the original domain Inkline.ca.
Page size can be reduced by 100.3 kB (64%)
155.9 kB
55.6 kB
In fact, the total size of Inkline.ca main page is 155.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. 55% of websites need less resources to load. HTML takes 122.7 kB which makes up the majority of the site volume.
Potential reduce by 100.2 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 100.2 kB or 82% of the original size.
Potential reduce by 109 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.
Number of requests can be reduced by 28 (85%)
33
5
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inkline. 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 14 to 1 for CSS and as a result speed up the page load time.
inkline.ca
513 ms
inkline.ca
242 ms
style.min.css
137 ms
cf-cartflows-defaults.css
147 ms
core-styles.6.10.2.css
130 ms
components-full.6.10.2.css
127 ms
mkhb-render.css
113 ms
mkhb-row.css
128 ms
mkhb-column.css
233 ms
js_composer.min.css
262 ms
theme-options-production-1717686979.css
249 ms
shortcodes-styles.min.css
279 ms
style.css
248 ms
jquery.min.js
299 ms
jquery-migrate.min.js
357 ms
iubenda_cs.js
356 ms
webfontloader.js
365 ms
js.cookie.js
367 ms
handl-utm-grabber.js
385 ms
dashicons.min.css
412 ms
flexslider.css
403 ms
gtm4wp-form-move-tracker.js
459 ms
core-scripts.6.10.2.js
502 ms
components-full.6.10.2.js
458 ms
mkhb-render.js
508 ms
mkhb-column.js
455 ms
shortcodes-scripts.min.js
535 ms
smush-lazy-load.min.js
562 ms
js_composer_front.min.js
582 ms
jquery.flexslider-min.js
667 ms
inkline-pattern.svg
235 ms
core-fcf8c9eac36aece9d290934b54a63296.js
77 ms
css
150 ms
inkline_primarylogo_white.svg
152 ms
inkline_primarylogo_blue.svg
154 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
20 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
29 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
32 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_N_XbMZhKg.ttf
30 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ObXbMZhKg.ttf
32 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_ArQbMZhKg.ttf
32 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf
32 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf
33 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_LjQbMZhKg.ttf
33 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjRbMZhKg.ttf
64 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf
65 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf
66 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf
67 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCTtINRLSzt.ttf
67 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCTNIJRLSzt.ttf
67 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCT6oJRLSzt.ttf
68 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCTtIJRLSzt.ttf
69 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCThoJRLSzt.ttf
69 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCTaoVRLSzt.ttf
69 ms
Qw3JZQNVED7rKGKxtqIqX5EUCGZ2dIn0FyA96fCTU4VRLSzt.ttf
68 ms
inkline.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
Image elements do not have [alt] attributes
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.
inkline.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
Missing source maps for large first-party JavaScript
inkline.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Inkline.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 Inkline.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.
inkline.ca
Open Graph data is detected on the main page of Inkline. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: