Tools & Wizards About Us
fundraise.brightpink.org screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fundraise.brightpink.org

Donate Landing — Bright Pink

Page Load Speed

1.1 sec in total

First Response

46 ms

Resources Loaded

958 ms

Page Rendered

98 ms

fundraise.brightpink.org screenshot

About Website

Welcome to fundraise.brightpink.org homepage info - get ready to check Fundraise Bright Pink best content for United States right away, or after learning these important things about fundraise.brightpink.org

Visit fundraise.brightpink.org

Key Findings

We analyzed Fundraise.brightpink.org page load time and found that the first response time was 46 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

fundraise.brightpink.org performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

fundraise.brightpink.org

46 ms

donate

68 ms

css2

524 ms

legacy.js

67 ms

modern.js

79 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Fundraise.brightpink.org, 53% (9 requests) were made to Assets.squarespace.com and 18% (3 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (524 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fundraise.brightpink.org main page is 1.2 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. 35% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 131.7 kB

  • Original 148.3 kB
  • After minification 82.8 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 65.4 kB, which is 44% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 131.7 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 40.5 kB
  • After minification 40.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. Fundraise Bright Pink images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 5.2 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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

-17%

Potential reduce by 3.1 kB

  • Original 18.7 kB
  • After minification 18.7 kB
  • After compression 15.6 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. Fundraise.brightpink.org needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (60%)

Requests Now

15

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fundraise.brightpink.org

fundraise.brightpink.org

46 ms

donate

donate

68 ms

css2

css2

524 ms

legacy.js

legacy.js

67 ms

modern.js

modern.js

79 ms

extract-css-runtime-8af0f70d1e8b3c253d2a-min.en-US.js

extract-css-runtime-8af0f70d1e8b3c253d2a-min.en-US.js

73 ms

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

extract-css-moment-js-vendor-6f117db4eb7fd4392375-min.en-US.js

97 ms

cldr-resource-pack-15305921bb94c505cd92-min.en-US.js

cldr-resource-pack-15305921bb94c505cd92-min.en-US.js

67 ms

common-vendors-stable-0f51b06fac4ba1f7c845-min.en-US.js

common-vendors-stable-0f51b06fac4ba1f7c845-min.en-US.js

87 ms

common-vendors-1540f1ad8308030d54a0-min.en-US.js

common-vendors-1540f1ad8308030d54a0-min.en-US.js

96 ms

common-78056ec09629ecee7e78-min.en-US.js

common-78056ec09629ecee7e78-min.en-US.js

100 ms

performance-7c5a1be54b087e14e57b-min.en-US.js

performance-7c5a1be54b087e14e57b-min.en-US.js

76 ms

site.css

site.css

92 ms

static.css

static.css

70 ms

site-bundle.ed46306c56a516420b3e44c437245ab5.js

site-bundle.ed46306c56a516420b3e44c437245ab5.js

74 ms

BP_MainLogo_RGB.png

BP_MainLogo_RGB.png

189 ms

donate-gray.gif

donate-gray.gif

219 ms

Accessibility Review

fundraise.brightpink.org accessibility score

90

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

<input type="image"> elements do not have [alt] text

Best Practices

fundraise.brightpink.org 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

fundraise.brightpink.org SEO score

93

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

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 Fundraise.brightpink.org 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 Fundraise.brightpink.org 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

fundraise.brightpink.org

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