3.3 sec in total
116 ms
2.9 sec
311 ms
Welcome to cantarus.com homepage info - get ready to check Cantarus best content right away, or after learning these important things about cantarus.com
Cantarus is a full service digital and web design agency in Manchester & London providing a comprehensive offering across web design, web development, mobile apps, online community, creative design an...
Visit cantarus.comWe analyzed Cantarus.com page load time and found that the first response time was 116 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cantarus.com performance score
name
value
score
weighting
Value4.1 s
20/100
10%
Value12.2 s
0/100
25%
Value8.0 s
22/100
10%
Value1,370 ms
16/100
30%
Value0.012
100/100
15%
Value20.3 s
2/100
10%
116 ms
197 ms
32 ms
156 ms
360 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 87% of them (69 requests) were addressed to the original Cantarus.com, 6% (5 requests) were made to Use.typekit.net and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Cantarus.com.
Page size can be reduced by 1.1 MB (51%)
2.2 MB
1.1 MB
In fact, the total size of Cantarus.com main page is 2.2 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. 35% of websites need less resources to load. Javascripts take 955.1 kB which makes up the majority of the site volume.
Potential reduce by 52.3 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 10.3 kB, which is 14% 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 52.3 kB or 71% of the original size.
Potential reduce by 5.7 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. Cantarus images are well optimized though.
Potential reduce by 703.5 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 703.5 kB or 74% of the original size.
Potential reduce by 336.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. Cantarus.com needs all CSS files to be minified and compressed as it can save up to 336.8 kB or 86% of the original size.
Number of requests can be reduced by 59 (82%)
72
13
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cantarus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
cantarus.com
116 ms
www.cantarus.com
197 ms
ZLETaLo2b1cXlTUHm6euQ9CtRwk.js
32 ms
default.css
156 ms
module.css
360 ms
module.css
365 ms
module.css
361 ms
module.css
136 ms
module.css
161 ms
module.css
241 ms
module.css
254 ms
module.css
261 ms
module.css
344 ms
module.css
1822 ms
module.css
358 ms
module.css
451 ms
module.css
457 ms
menu.css
459 ms
menu.css
446 ms
foundation.css
480 ms
foundation-icons.css
549 ms
animate.css
553 ms
normalize.css
560 ms
idangerous.swiper.css
578 ms
skin.css
577 ms
Home.css
655 ms
container.css
673 ms
portal.css
655 ms
module.css
677 ms
jquery.js
708 ms
jquery-migrate.js
988 ms
jquery-ui.js
781 ms
WebResource.axd
771 ms
Telerik.Web.UI.WebResource.axd
807 ms
foundation.min.js
851 ms
dnn.js
876 ms
dnn.modalpopup.js
1101 ms
iag7mbd.js
225 ms
jquery.hoverIntent.min.js
907 ms
infobox.js
932 ms
jquery.dnnmega.js
870 ms
clientlogos.js
870 ms
dnn.jquery.js
908 ms
newsblogs.js
853 ms
jquery.viewportchecker.js
844 ms
animate.js
873 ms
sharedscripts.js
822 ms
jquery.BlackAndWhite.js
842 ms
moment.min.js
843 ms
dnncore.js
852 ms
idangerous.swiper.js
883 ms
QuickContactForm.js
820 ms
BrochureContactForm.js
862 ms
slider.js
1065 ms
Support.js
878 ms
dnn.analytics.Injected.js
861 ms
--efNuyHEVktwd9qSOI0bXR6GL8.js
719 ms
css;charset=utf-8;base64,Y2xvdWRmbGFyZS1hcHBbYXBwLWlkPSJhLWJldHRlci1icm93c2VyIl0gewogIGRpc3BsYXk6IGJsb2NrOwogIGJhY2tncm91bmQ6ICM0NTQ4NGQ7CiAgY29sb3I6ICNmZmY7CiAgbGluZS1oZWlnaHQ6IDEuNDU7CiAgcG9zaXRpb246IGZpeGVkOwogIHotaW5kZXg6IDkwMDAwMDAwOwogIHRvcDogMDsKICBsZWZ0OiAwOwogIHJpZ2h0OiAwOwogIHBhZGRpbmc6IC41ZW0gMWVtOwogIHRleHQtYWxpZ246IGNlbnRlcjsKICAtd2Via2l0LXVzZXItc2VsZWN0OiBub25lOwogICAgIC1tb3otdXNlci1zZWxlY3Q6IG5vbmU7CiAgICAgIC1tcy11c2VyLXNlbGVjdDogbm9uZTsKICAgICAgICAgIHVzZXItc2VsZWN0OiBub25lOwp9CgpjbG91ZGZsYXJlLWFwcFthcHAtaWQ9ImEtYmV0dGVyLWJyb3dzZXIiXVtkYXRhLXZpc2liaWxpdHk9ImhpZGRlbiJdIHsKICBkaXNwbGF5OiBub25lOwp9CgpjbG91ZGZsYXJlLWFwcFthcHAtaWQ9ImEtYmV0dGVyLWJyb3dzZXIiXSBjbG91ZGZsYXJlLWFwcC1tZXNzYWdlIHsKICBkaXNwbGF5OiBibG9jazsKfQoKY2xvdWRmbGFyZS1hcHBbYXBwLWlkPSJhLWJldHRlci1icm93c2VyIl0gYSB7CiAgdGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmU7CiAgY29sb3I6ICNlYmViZjQ7Cn0KCmNsb3VkZmxhcmUtYXBwW2FwcC1pZD0iYS1iZXR0ZXItYnJvd3NlciJdIGE6aG92ZXIsCmNsb3VkZmxhcmUtYXBwW2FwcC1pZD0iYS1iZXR0ZXItYnJvd3NlciJdIGE6YWN0aXZlIHsKICBjb2xvcjogI2RiZGJlYjsKfQoKY2xvdWRmbGFyZS1hcHBbYXBwLWlkPSJhLWJldHRlci1icm93c2VyIl0gY2xvdWRmbGFyZS1hcHAtY2xvc2UgewogIGRpc3BsYXk6IGJsb2NrOwogIGN1cnNvcjogcG9pbnRlcjsKICBmb250LXNpemU6IDEuNWVtOwogIHBvc2l0aW9uOiBhYnNvbHV0ZTsKICByaWdodDogLjRlbTsKICB0b3A6IC4zNWVtOwogIGhlaWdodDogMWVtOwogIHdpZHRoOiAxZW07CiAgbGluZS1oZWlnaHQ6IDE7Cn0KCmNsb3VkZmxhcmUtYXBwW2FwcC1pZD0iYS1iZXR0ZXItYnJvd3NlciJdIGNsb3VkZmxhcmUtYXBwLWNsb3NlOmFjdGl2ZSB7CiAgLXdlYmtpdC10cmFuc2Zvcm06IHRyYW5zbGF0ZVkoMXB4KTsKICAgICAgICAgIHRyYW5zZm9ybTogdHJhbnNsYXRlWSgxcHgpOwp9CgpjbG91ZGZsYXJlLWFwcFthcHAtaWQ9ImEtYmV0dGVyLWJyb3dzZXIiXSBjbG91ZGZsYXJlLWFwcC1jbG9zZTpob3ZlciB7CiAgb3BhY2l0eTogLjllbTsKICBjb2xvcjogI2ZmZjsKfQo=
0 ms
ga.js
133 ms
menu-bg.png
174 ms
sprite-sheet.png
157 ms
cantarus-logo.png
298 ms
Cantarus-banner-1.jpg
364 ms
%20Cantarus-banner-2.jpg
296 ms
%20Cantarus-banner-3.jpg
356 ms
%20Cantarus-banner-4.jpg
436 ms
Cantarus-banner-1-mobile.jpg
363 ms
controls.png
319 ms
website.png
349 ms
business.png
416 ms
hosting.png
484 ms
services.png
473 ms
d
38 ms
d
154 ms
d
179 ms
d
178 ms
__utm.gif
50 ms
p.gif
162 ms
__utm.gif
21 ms
cantarus.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible 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
Heading elements are not in a sequentially-descending order
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.
cantarus.com 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
cantarus.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cantarus.com 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 Cantarus.com 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.
cantarus.com
Open Graph description is not detected on the main page of Cantarus. 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: