Tools & Wizards About Us

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

waiting.com

Coma and Traumatic Brain Injury Information for Families and Survivors

Page Load Speed

452 ms in total

First Response

102 ms

Resources Loaded

230 ms

Page Rendered

120 ms

About Website

Welcome to waiting.com homepage info - get ready to check Waiting best content for United States right away, or after learning these important things about waiting.com

Coma waiting page: Information and Resources about coma and traumatic brain injury for those who are waiting for someone to emerge from a coma.

Visit waiting.com

Key Findings

We analyzed Waiting.com page load time and found that the first response time was 102 ms and then it took 350 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

waiting.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value1,970 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

waiting.com

102 ms

AC_RunActiveContent.js

35 ms

ga.js

6 ms

cdn.zopim.com

30 ms

newbackground.jpg

38 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 60% of them (6 requests) were addressed to the original Waiting.com, 20% (2 requests) were made to Google-analytics.com and 10% (1 request) were made to Cdn.zopim.com. The less responsive or slowest element that took the longest time to load (102 ms) belongs to the original domain Waiting.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.4 kB (15%)

Content Size

57.1 kB

After Optimization

48.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Waiting.com main page is 57.1 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. Only 10% of websites need less resources to load. Javascripts take 24.5 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 4.8 kB

  • Original 8.1 kB
  • After minification 7.7 kB
  • After compression 3.3 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 4.8 kB or 59% of the original size.

Image Optimization

-5%

Potential reduce by 1.2 kB

  • Original 24.5 kB
  • After minification 23.3 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. Waiting images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 2.4 kB

  • Original 24.5 kB
  • After minification 23.7 kB
  • After compression 22.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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

  • Images
  • JavaScript

The browser has sent 8 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waiting. According to our analytics all requests are already optimized.

Network Requests Diagram

Accessibility Review

waiting.com accessibility score

88

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

waiting.com best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

waiting.com 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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waiting.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 Waiting.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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