Tools & Wizards About Us
heartline.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

heartline.com

The HEARTLINE Study: Research study to improve AFib outcomes

Page Load Speed

1.9 sec in total

First Response

66 ms

Resources Loaded

1.1 sec

Page Rendered

696 ms

heartline.com screenshot

About Website

Click here to check amazing HEARTLINE content for United States. Otherwise, check out these important facts you probably never knew about heartline.com

The HEARTLINE Study from Johnson & Johnson in collaboration with Apple will analyze the impact of Apple Watch on AFib diagnosis and the prevention of stroke.

Visit heartline.com

Key Findings

We analyzed Heartline.com page load time and found that the first response time was 66 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

heartline.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value2.8 s

95/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.132

81/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

heartline.com

66 ms

heartline.com

112 ms

css

33 ms

css

46 ms

main.bb18a926.js

64 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 16% of them (5 requests) were addressed to the original Heartline.com, 45% (14 requests) were made to Assets.prod.heartline.com and 10% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (480 ms) belongs to the original domain Heartline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 304.6 kB (11%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heartline.com main page is 2.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 15.1 kB

  • Original 21.3 kB
  • After minification 21.3 kB
  • After compression 6.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. 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 15.1 kB or 71% of the original size.

Image Optimization

-11%

Potential reduce by 289.4 kB

  • Original 2.5 MB
  • After minification 2.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, HEARTLINE needs image optimization as it can save up to 289.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 296.1 kB
  • After minification 296.1 kB
  • After compression 296.0 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

-6%

Potential reduce by 64 B

  • Original 1.1 kB
  • After minification 1.1 kB
  • After compression 1.0 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. Heartline.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (16%)

Requests Now

25

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heartline.com

heartline.com

66 ms

heartline.com

heartline.com

112 ms

css

css

33 ms

css

css

46 ms

main.bb18a926.js

main.bb18a926.js

64 ms

main.f866af6e.css

main.f866af6e.css

480 ms

analytics.js

analytics.js

318 ms

fbevents.js

fbevents.js

281 ms

heartline-logo.jpg

heartline-logo.jpg

391 ms

lookup

lookup

184 ms

badge-enrollment-closed-108w@2x.png

badge-enrollment-closed-108w@2x.png

179 ms

get-the-app-50w@2x.png

get-the-app-50w@2x.png

187 ms

j-j-logosignature-rgb-red.png

j-j-logosignature-rgb-red.png

215 ms

technology-280w@2x.png

technology-280w@2x.png

188 ms

02-Study-Phones-01-270x530@2x.png

02-Study-Phones-01-270x530@2x.png

218 ms

02-Study-Phones-02-270x530@2x.png

02-Study-Phones-02-270x530@2x.png

238 ms

02-Study-Phones-03-270x530@2x.png

02-Study-Phones-03-270x530@2x.png

216 ms

US-residents-200w@2x.png

US-residents-200w@2x.png

190 ms

03-Eligible-IconPhones-200x200-Desktop@2x.png

03-Eligible-IconPhones-200x200-Desktop@2x.png

189 ms

original-medicare-200w@2x.png

original-medicare-200w@2x.png

222 ms

05-Reviews-5Stars-Small-96x20-Both@2x.png

05-Reviews-5Stars-Small-96x20-Both@2x.png

240 ms

06-Privacy-Photo-740x500@2x.png

06-Privacy-Photo-740x500@2x.png

261 ms

lineto-circular-book.woff

lineto-circular-book.woff

374 ms

jizAREVNn1dOx-zrZ2X3pZvkTi3A_yI0q14.ttf

jizAREVNn1dOx-zrZ2X3pZvkTi3A_yI0q14.ttf

109 ms

jizAREVNn1dOx-zrZ2X3pZvkTi3s-CI0q14.ttf

jizAREVNn1dOx-zrZ2X3pZvkTi3s-CI0q14.ttf

119 ms

jizDREVNn1dOx-zrZ2X3pZvkTiUf2zI.ttf

jizDREVNn1dOx-zrZ2X3pZvkTiUf2zI.ttf

175 ms

426834258593087

426834258593087

86 ms

collect

collect

17 ms

collect

collect

43 ms

05-Reviews-4_5Stars-Small-96x20-Both@2x.png

05-Reviews-4_5Stars-Small-96x20-Both@2x.png

155 ms

ga-audiences

ga-audiences

71 ms

Accessibility Review

heartline.com accessibility score

95

Accessibility Issues

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.

Tables and lists

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

Impact

Issue

High

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

Best Practices

heartline.com best practices score

75

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

heartline.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

heartline.com

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