Tools & Wizards About Us
curam.io screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

curam.io

Curam | UK's Leading Online Source of Private Carers

Page Load Speed

2.6 sec in total

First Response

202 ms

Resources Loaded

1.8 sec

Page Rendered

650 ms

curam.io screenshot

About Website

Click here to check amazing Curam content. Otherwise, check out these important facts you probably never knew about curam.io

At Curam, we put choice at the heart of care. By connecting you with trusted and experienced carers, we will help you find the best carer for your needs.

Visit curam.io

Key Findings

We analyzed Curam.io page load time and found that the first response time was 202 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

curam.io performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value16,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.962

2/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

Network Requests Diagram

curam.io

202 ms

www.curamcare.com

457 ms

widget.js

177 ms

first_fold.css

79 ms

hidden.module.css

157 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Curam.io, 64% (61 requests) were made to Curamcare.com and 16% (15 requests) were made to Cdn.curamcare.com. The less responsive or slowest element that took the longest time to load (532 ms) relates to the external source Curamcare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 116.4 kB (37%)

Content Size

311.2 kB

After Optimization

194.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Curam.io main page is 311.2 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. 60% of websites need less resources to load. Javascripts take 137.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 111.6 kB

  • Original 136.5 kB
  • After minification 121.1 kB
  • After compression 25.0 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 15.4 kB, which is 11% 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 111.6 kB or 82% of the original size.

JavaScript Optimization

-1%

Potential reduce by 1.3 kB

  • Original 137.5 kB
  • After minification 137.4 kB
  • After compression 136.1 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.

CSS Optimization

-9%

Potential reduce by 3.5 kB

  • Original 37.1 kB
  • After minification 36.8 kB
  • After compression 33.6 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. Curam.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 47 (66%)

Requests Now

71

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

curam.io

curam.io

202 ms

www.curamcare.com

www.curamcare.com

457 ms

widget.js

widget.js

177 ms

first_fold.css

first_fold.css

79 ms

hidden.module.css

hidden.module.css

157 ms

views.module.css

views.module.css

373 ms

styles.css

styles.css

230 ms

footer-component.css

footer-component.css

228 ms

header-component.css

header-component.css

230 ms

cookies.css

cookies.css

373 ms

home-page-content-component.css

home-page-content-component.css

235 ms

owl.carousel.min.css

owl.carousel.min.css

306 ms

css_MFIYr_T1Vv2-6Hi7NIbr2AB-1hhKgVT5Z05SM1qx2Dc._1fBoBGkLlQUfgXMYMBzCXOmWK8wJ4S6p2jeVwdbou4.css

css_MFIYr_T1Vv2-6Hi7NIbr2AB-1hhKgVT5Z05SM1qx2Dc._1fBoBGkLlQUfgXMYMBzCXOmWK8wJ4S6p2jeVwdbou4.css

305 ms

custom-homepage.css

custom-homepage.css

308 ms

e7bf4c0b7f154a90ced902c27f3ddfe0.js

e7bf4c0b7f154a90ced902c27f3ddfe0.js

144 ms

get-script

get-script

44 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

19 ms

jquery.min.js

jquery.min.js

386 ms

underscore-min.js

underscore-min.js

379 ms

jquery.once.min.js

jquery.once.min.js

378 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

382 ms

drupal.js

drupal.js

443 ms

drupal.init.js

drupal.init.js

445 ms

rti_settings.js

rti_settings.js

455 ms

homepage.js

homepage.js

457 ms

home-banner.js

home-banner.js

460 ms

js_Qoa6l5lYRyN29xNxhGSkb_hH8s6uWW_-595NMNexSJU.pTxD-DSzIwmwhOqTFN-DB-nHjO4iAsbgfyFq5K5bcE0.js

js_Qoa6l5lYRyN29xNxhGSkb_hH8s6uWW_-595NMNexSJU.pTxD-DSzIwmwhOqTFN-DB-nHjO4iAsbgfyFq5K5bcE0.js

462 ms

lazysizes.min.js

lazysizes.min.js

520 ms

jquery.md5.min.js

jquery.md5.min.js

523 ms

gtm-datalayers.js

gtm-datalayers.js

532 ms

first_fold.css

first_fold.css

365 ms

css2

css2

28 ms

first_fold.css

first_fold.css

163 ms

gtm.js

gtm.js

162 ms

play-icon.webp

play-icon.webp

164 ms

ajax-loader.gif

ajax-loader.gif

279 ms

humburger-menu.svg

humburger-menu.svg

146 ms

Curam_logo.svg

Curam_logo.svg

143 ms

dropdown-close-icon.svg

dropdown-close-icon.svg

146 ms

dropdown-open-icon.svg

dropdown-open-icon.svg

142 ms

type-of-care-icon.svg

type-of-care-icon.svg

144 ms

type-of-care-icon-active.svg

type-of-care-icon-active.svg

254 ms

how-it-work-icon.svg

how-it-work-icon.svg

256 ms

how-it-work-icon-active.webp

how-it-work-icon-active.webp

253 ms

cost-calculator-icon.svg

cost-calculator-icon.svg

255 ms

cost-calculator-icon-active.webp

cost-calculator-icon-active.webp

253 ms

location-Icon.svg

location-Icon.svg

289 ms

location-icon-active.webp

location-icon-active.webp

291 ms

get-started-icon.svg

get-started-icon.svg

291 ms

search-icon.svg

search-icon.svg

293 ms

search-icon-active.webp

search-icon-active.webp

293 ms

become-registered-carer-icon.svg

become-registered-carer-icon.svg

350 ms

login-icon.svg

login-icon.svg

367 ms

nav-close.svg

nav-close.svg

367 ms

nav-arrow.svg

nav-arrow.svg

368 ms

for-carer.svg

for-carer.svg

369 ms

for-business.svg

for-business.svg

370 ms

blog-icon.svg

blog-icon.svg

446 ms

help-icon.svg

help-icon.svg

443 ms

nav-back-arrow-icon.svg

nav-back-arrow-icon.svg

444 ms

why-be-curamcare.svg

why-be-curamcare.svg

444 ms

header-support-phone.svg

header-support-phone.svg

446 ms

curam-bg.svg

curam-bg.svg

447 ms

search_icon.webp

search_icon.webp

519 ms

header-support-phone.webp

header-support-phone.webp

523 ms

chevronright.webp

chevronright.webp

522 ms

location-icon.webp

location-icon.webp

521 ms

location-icon-error.svg

location-icon-error.svg

524 ms

pause-icon.webp

pause-icon.webp

179 ms

curam-meet.webp

curam-meet.webp

196 ms

how-it-works-number.webp

how-it-works-number.webp

196 ms

carers_home.webp

carers_home.webp

202 ms

Curam_logo_white.svg

Curam_logo_white.svg

197 ms

store-google.svg

store-google.svg

202 ms

store-ios.svg

store-ios.svg

198 ms

footer-email-icon.webp

footer-email-icon.webp

202 ms

footer-call-icon.webp

footer-call-icon.webp

203 ms

footer-location-icon.webp

footer-location-icon.webp

220 ms

fb.svg

fb.svg

222 ms

twitter.svg

twitter.svg

226 ms

insta.svg

insta.svg

224 ms

linkdin.svg

linkdin.svg

225 ms

average-carousel-rating-widget

average-carousel-rating-widget

93 ms

average-rating-widget

average-rating-widget

89 ms

tick-green.svg

tick-green.svg

485 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_F.ttf

109 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_F.ttf

117 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_F.ttf

146 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_F.ttf

206 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_F.ttf

181 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_F.ttf

179 ms

widget_app_base_1725367019229.js

widget_app_base_1725367019229.js

59 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

80 ms

global.css

global.css

22 ms

average-carousel-review.js

average-carousel-review.js

24 ms

average-rating.js

average-rating.js

32 ms

Accessibility Review

curam.io accessibility score

94

Accessibility Issues

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

High

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

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

curam.io best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

curam.io SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

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 Curam.io 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 Curam.io 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

curam.io

Open Graph data is detected on the main page of Curam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: