2.7 sec in total
175 ms
2 sec
574 ms
Welcome to orcare.com homepage info - get ready to check Orcare best content right away, or after learning these important things about orcare.com
Carbon Six Digital are experienced Umbraco developers. We build agile, responsive Websites and Webapps using Umbraco.
Visit orcare.comWe analyzed Orcare.com page load time and found that the first response time was 175 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
orcare.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value8.2 s
2/100
25%
Value7.7 s
24/100
10%
Value1,880 ms
9/100
30%
Value0.363
30/100
15%
Value16.7 s
5/100
10%
175 ms
319 ms
178 ms
339 ms
101 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Orcare.com, 58% (30 requests) were made to Carbonsix.digital and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (487 ms) relates to the external source Carbonsix.digital.
Page size can be reduced by 468.9 kB (38%)
1.2 MB
759.7 kB
In fact, the total size of Orcare.com main page is 1.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. 60% of websites need less resources to load. Images take 856.9 kB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 13.9 kB, which is 30% 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 38.2 kB or 83% of the original size.
Potential reduce by 380.5 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. Obviously, Orcare needs image optimization as it can save up to 380.5 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 26.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 26.5 kB or 11% of the original size.
Potential reduce by 23.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. Orcare.com needs all CSS files to be minified and compressed as it can save up to 23.7 kB or 31% of the original size.
Number of requests can be reduced by 25 (56%)
45
20
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Orcare. 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 from 6 to 1 for CSS and as a result speed up the page load time.
orcare.com
175 ms
orcare.com
319 ms
carbonsix.digital
178 ms
carbonsix.digital
339 ms
bootstrap.min.css
101 ms
jquery.fancybox.min.css
185 ms
animate.min.css
274 ms
style.min.css
421 ms
modernizr-custom.js
343 ms
jquery-2.1.1.min.js
45 ms
v2.js
55 ms
font-awesome.min.css
347 ms
social-icons.min.css
348 ms
jquery-ui.min.js
38 ms
bootstrap.min.js
349 ms
mobile.min.js
351 ms
scripts.js
487 ms
cookies.js
487 ms
gtm.js
133 ms
logo.png
94 ms
home-intro-grey.jpg
451 ms
harwoods-group-logo.png
91 ms
little-freddie-logo.png
93 ms
wasps-s.png
94 ms
cbs-s.png
123 ms
jncc.png
180 ms
nextbase-s.png
181 ms
platinum_vertical_partner_badge.png
259 ms
umbraco-instant-health-check-no-shapes.png
327 ms
umb-heart.png
437 ms
Carbon-Six_bg.png
243 ms
social-001.jpg
327 ms
fontawesome-webfont.woff
340 ms
jquery.matchHeight.min.js
315 ms
smoothscroll.min.js
324 ms
bat.js
46 ms
analytics.js
47 ms
hotjar-2052954.js
121 ms
loader.js
45 ms
541037.js
88 ms
collect
20 ms
call-tracking_9.js
5 ms
carbon-six_bg.png
195 ms
collect
57 ms
js
65 ms
banner.js
172 ms
leadflows.js
184 ms
conversations-embed.js
161 ms
541037.js
170 ms
modules.305879d9d5e96288a7f4.js
31 ms
wcm
124 ms
ga-audiences
175 ms
orcare.com 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.
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
ARIA IDs are not unique
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.
orcare.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
Page has valid source maps
orcare.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Orcare.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 Orcare.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.
orcare.com
Open Graph data is detected on the main page of Orcare. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: