Tools & Wizards About Us

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

folife.org

Home | File of Life

Page Load Speed

387 ms in total

First Response

124 ms

Resources Loaded

208 ms

Page Rendered

55 ms

About Website

Visit folife.org now to see the best up-to-date Fo Life content and also check out these interesting facts you probably never knew about folife.org

File of Life gives first responders medical information when patients can't. Including allergies, medications, contact persons and more

Visit folife.org

Key Findings

We analyzed Folife.org page load time and found that the first response time was 124 ms and then it took 263 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

folife.org performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

folife.org

124 ms

follow_bird-a.png

35 ms

f_logo.jpg

11 ms

greyback.gif

21 ms

pinkmarbline.gif

19 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 83% of them (5 requests) were addressed to the original Folife.org, 17% (1 request) were made to Twitter-badges.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (124 ms) belongs to the original domain Folife.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 kB (34%)

Content Size

6.7 kB

After Optimization

4.4 kB

  • HTML
  • Images

In fact, the total size of Folife.org main page is 6.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 4.3 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 1.5 kB

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 889 B

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 1.5 kB or 62% of the original size.

Image Optimization

-18%

Potential reduce by 767 B

  • Original 4.3 kB
  • After minification 3.6 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. Obviously, Fo Life needs image optimization as it can save up to 767 B or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • Images

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

Network Requests Diagram

Accessibility Review

folife.org accessibility score

65

Accessibility Issues

Internationalization and localization

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

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

Best Practices

folife.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

folife.org SEO score

54

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Folife.org 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 Folife.org main page’s claimed encoding is . 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 Fo Life. 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: