Access careoncall.co.nz. In Home Care Services | Home Help

name

value

score

weighting

FCP (First Contentful Paint)

Value14.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.5 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

careoncall.co.nz

633 ms

www.careoncall.nz

598 ms

www.careoncall.nz

1261 ms

gtm.js

64 ms

default.css

809 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Careoncall.co.nz, 88% (64 requests) were made to Careoncall.nz and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Careoncall.nz.

Content Size

6.4 MB

After Optimization

3.6 MB

In fact, the total size of Careoncall.co.nz main page is 6.4 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 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 44.8 kB

Original 60.0 kB
After minification 49.7 kB
After compression 15.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 10.3 kB, which is 17% 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 44.8 kB or 75% of the original size.

Image Optimization

-31%

Potential reduce by 1.4 MB

Original 4.6 MB
After minification 3.2 MB

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, Care Oncall needs image optimization as it can save up to 1.4 MB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 835.5 kB

Original 1.1 MB
After minification 895.4 kB
After compression 291.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 835.5 kB or 74% of the original size.

CSS Optimization

-85%

Potential reduce by 470.5 kB

Original 552.7 kB
After minification 458.3 kB
After compression 82.2 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. Careoncall.co.nz needs all CSS files to be minified and compressed as it can save up to 470.5 kB or 85% of the original size.

Requests Now

After Optimization

The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Care Oncall. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

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.

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Careoncall.co.nz 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 Careoncall.co.nz 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.

Social Sharing Optimization

careoncall.co.nz

Open Graph description is not detected on the main page of Care Oncall. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

In Home Care Services | Home Help | Caregivers

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

careoncall.co.nz

www.careoncall.nz

www.careoncall.nz

gtm.js

default.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

careoncall.co.nz

www.careoncall.nz

www.careoncall.nz

gtm.js

default.css

bootstrap.min.css

slick.css

all.css

jquery.fancybox.min.css

jquery.mmenu.all.css

skin.css

jquery.mmenu.pageshadow.css

home.css

jquery.js

jquery-ui.js

WebResource.axd

ScriptResource.axd

ScriptResource.axd

bootstrap.min.js

slick.min.js

jquery.fancybox.min.js

jquery.mmenu.min.all.js

jquery.parallax.js

jquery.livequery.min.js

jquery.fontscale.min.js

TweenLite.min.js

skin.js

EasePack.min.js

rAF.js

jquery.cookie.js

dnn.modalpopup.js

dnncore.js

addthis_widget.js

css

logo.png

pattern.jpg

1.png

2.png

3.png

4.png

5.png

6.png

7.png