Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

goodforgood.com

Writer Presenter Food Campaigner | Danny McCubbin | Mussomeli

Page Load Speed

2.5 sec in total

First Response

372 ms

Resources Loaded

2 sec

Page Rendered

85 ms

About Website

Click here to check amazing Goodforgood content. Otherwise, check out these important facts you probably never knew about goodforgood.com

I launched a community kitchen here in this remote town in Sicily called Mussomeli. Every week I rescue surplus food from a market in Caltanisetta and then I use that food to cook for vulnerable peopl...

Visit goodforgood.com

Key Findings

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

Performance Metrics

goodforgood.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

www.goodforgood.com

372 ms

minified.js

33 ms

focus-within-polyfill.js

31 ms

polyfill.min.js

846 ms

thunderbolt-commons.7700cd07.bundle.min.js

4 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Goodforgood.com, 36% (15 requests) were made to Static.parastorage.com and 29% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (846 ms) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 613.8 kB (41%)

Content Size

1.5 MB

After Optimization

894.4 kB

In fact, the total size of Goodforgood.com main page is 1.5 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. 25% of websites need less resources to load. HTML takes 655.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 536.7 kB

  • Original 655.2 kB
  • After minification 653.4 kB
  • After compression 118.5 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 536.7 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 29.0 kB

  • Original 549.4 kB
  • After minification 520.5 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. Goodforgood images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 303.5 kB
  • After minification 303.5 kB
  • After compression 255.4 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (38%)

Requests Now

26

After Optimization

16

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

Accessibility Review

goodforgood.com accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Page has valid source maps

SEO Factors

goodforgood.com SEO score

99

Search Engine Optimization Advices

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

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