Access 1heartcares.com. Caregivers in Los Angeles and Around California

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,410 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.809

5/100

15%

TTI (Time to Interactive)

Value26.7 s

0/100

10%

1heartcares.com

130 ms

1heartcares.com

434 ms

gtm.js

52 ms

js

67 ms

e73712940ef9ac617b1f47a6f0b1646a.css

79 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 67% of them (73 requests) were addressed to the original 1heartcares.com, 7% (8 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (851 ms) belongs to the original domain 1heartcares.com.

Content Size

2.4 MB

After Optimization

1.9 MB

In fact, the total size of 1heartcares.com main page is 2.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. Only a small number of websites need less resources to load. Javascripts take 925.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 287.4 kB

Original 348.4 kB
After minification 344.0 kB
After compression 60.9 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 287.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 909.8 kB
After minification 909.8 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. 1Heart Cares images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 224.6 kB

Original 925.8 kB
After minification 925.8 kB
After compression 701.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 224.6 kB or 24% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

Original 242.5 kB
After minification 242.5 kB
After compression 242.5 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. 1heartcares.com has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1Heart Cares. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts 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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

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

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1heartcares.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 1heartcares.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.

Social Sharing Optimization

1heartcares.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Caregivers in Los Angeles and Around California | 1Heart

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

1heartcares.com

1heartcares.com

gtm.js

js

e73712940ef9ac617b1f47a6f0b1646a.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

1heartcares.com

1heartcares.com

gtm.js

js

e73712940ef9ac617b1f47a6f0b1646a.css

jquery.min.js

jquery-migrate.min.js

jquery.themepunch.tools.min.js

jquery.themepunch.revolution.min.js

flatpickr.min.js

select2.min.js

css

js

fbevents.js

ytc.js

8ro5keejt8

EYkB4YTkHDc

ctct-plugin-recaptcha-v2.min.js

api.js

ctct-plugin-frontend.min.js

frontend.min.js

core.min.js

mouse.min.js

sortable.min.js

tabs.min.js

accordion.min.js

plugins.js

menu.js

animations.min.js

jplayer.min.js

translate3d.js

smoothscroll.js

scripts.js

api.js

main.js

js_composer_front.min.js

lightbox.min.js

owl.carousel.min.js

imagesloaded.pkgd.min.js

underscore.min.js

vc-waypoints.min.js

vc_grid.min.js

new-logo.png