Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

funraisin.co

Funraisin: Advanced online fundraising for nonprofits

Page Load Speed

27.9 sec in total

First Response

413 ms

Resources Loaded

18.9 sec

Page Rendered

8.6 sec

About Website

Click here to check amazing Funraisin content for Australia. Otherwise, check out these important facts you probably never knew about funraisin.co

Funraisin is the speciality events fundraising platform of choice for evolving nonprofits to better manage their P2P events, community fundraising and appeals.

Visit funraisin.co

Key Findings

We analyzed Funraisin.co page load time and found that the first response time was 413 ms and then it took 27.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

funraisin.co performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

funraisin.co

413 ms

www.funraisin.co

421 ms

www.funraisin.co

1380 ms

jquery-3.5.1.min.js

46 ms

jquery-migrate-3.3.1.min.js

56 ms

Our browser made a total of 202 requests to load all elements on the main page. We found that 10% of them (21 requests) were addressed to the original Funraisin.co, 50% (102 requests) were made to D1gotx1r5o7hbd.cloudfront.net and 24% (49 requests) were made to Dvtuw1sdeyetv.cloudfront.net. The less responsive or slowest element that took the longest time to load (7.1 sec) relates to the external source D1gotx1r5o7hbd.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (12%)

Content Size

9.4 MB

After Optimization

8.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funraisin.co main page is 9.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 409.2 kB

  • Original 472.0 kB
  • After minification 412.4 kB
  • After compression 62.9 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 59.6 kB, which is 13% 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 409.2 kB or 87% of the original size.

Image Optimization

-9%

Potential reduce by 710.1 kB

  • Original 8.3 MB
  • After minification 7.5 MB

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. Funraisin images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 11.7 kB

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

CSS Optimization

-8%

Potential reduce by 7.1 kB

  • Original 92.1 kB
  • After minification 92.1 kB
  • After compression 85.0 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. Funraisin.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 78 (43%)

Requests Now

180

After Optimization

102

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

funraisin.co accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role] values are not valid

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

funraisin.co best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

funraisin.co SEO score

79

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funraisin.co 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 Funraisin.co 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 Funraisin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: