Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 0

    Best Practices

  • 88

    SEO

    Google-friendlier than
    66% of websites

strokesupport.in

Stroke Support India – Know Stroke to Beat Stroke !

Page Load Speed

11.9 sec in total

First Response

4.5 sec

Resources Loaded

7.1 sec

Page Rendered

252 ms

strokesupport.in screenshot

About Website

Visit strokesupport.in now to see the best up-to-date Stroke Support content and also check out these interesting facts you probably never knew about strokesupport.in

Our Mission : To spread Stroke Awareness and support Stroke Survivors and Caregivers in India

Visit strokesupport.in

Key Findings

We analyzed Strokesupport.in page load time and found that the first response time was 4.5 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

strokesupport.in performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value11,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

strokesupport.in

4502 ms

wp-emoji-release.min.js

184 ms

toolbar.css

182 ms

style.css

243 ms

bbpress.css

186 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 69% of them (47 requests) were addressed to the original Strokesupport.in, 7% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Strokesupport.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 770.3 kB (73%)

Content Size

1.1 MB

After Optimization

284.3 kB

In fact, the total size of Strokesupport.in main page is 1.1 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. 65% of websites need less resources to load. CSS take 519.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 60.0 kB

  • Original 74.1 kB
  • After minification 72.8 kB
  • After compression 14.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. 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 60.0 kB or 81% of the original size.

JavaScript Optimization

-57%

Potential reduce by 261.8 kB

  • Original 460.8 kB
  • After minification 410.1 kB
  • After compression 199.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 261.8 kB or 57% of the original size.

CSS Optimization

-86%

Potential reduce by 448.5 kB

  • Original 519.6 kB
  • After minification 441.9 kB
  • After compression 71.1 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. Strokesupport.in needs all CSS files to be minified and compressed as it can save up to 448.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (92%)

Requests Now

60

After Optimization

5

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

Accessibility Review

strokesupport.in accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

SEO Factors

strokesupport.in SEO score

88

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

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 Strokesupport.in 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 Strokesupport.in 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

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