Tools & Wizards About Us
faavo.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

faavo.jp

クラウドファンディング - CAMPFIRE (キャンプファイヤー)

Page Load Speed

12.1 sec in total

First Response

367 ms

Resources Loaded

8.1 sec

Page Rendered

3.6 sec

faavo.jp screenshot

About Website

Visit faavo.jp now to see the best up-to-date Faavo content for Japan and also check out these interesting facts you probably never knew about faavo.jp

国内最大クラウドファンディング。最新ガジェット、ご当地グルメ、エンタメ、まちづくり…ジャンル規模問わず新しい挑戦が毎日登場!掲載件数70,000件以上。

Visit faavo.jp

Key Findings

We analyzed Faavo.jp page load time and found that the first response time was 367 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

faavo.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value4,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

faavo.jp

367 ms

faavo.jp

2212 ms

normalize.min.css

165 ms

main.css

751 ms

style.css

762 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 46% of them (29 requests) were addressed to the original Faavo.jp, 37% (23 requests) were made to Faavo-images.s3-ap-northeast-1.amazonaws.com and 6% (4 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Faavo-images.s3-ap-northeast-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.2 kB (23%)

Content Size

850.2 kB

After Optimization

656.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Faavo.jp main page is 850.2 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. 50% of websites need less resources to load. Images take 560.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 56.8 kB

  • Original 67.5 kB
  • After minification 49.0 kB
  • After compression 10.7 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 18.5 kB, which is 27% 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 56.8 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 3.2 kB

  • Original 560.8 kB
  • After minification 557.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. Faavo images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 41.8 kB

  • Original 115.0 kB
  • After minification 110.2 kB
  • After compression 73.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 41.8 kB or 36% of the original size.

CSS Optimization

-86%

Potential reduce by 92.4 kB

  • Original 106.9 kB
  • After minification 77.9 kB
  • After compression 14.5 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. Faavo.jp needs all CSS files to be minified and compressed as it can save up to 92.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (32%)

Requests Now

37

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faavo. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

faavo.jp

faavo.jp

367 ms

faavo.jp

faavo.jp

2212 ms

normalize.min.css

normalize.min.css

165 ms

main.css

main.css

751 ms

style.css

style.css

762 ms

jquery-ui.css

jquery-ui.css

54 ms

modernizr-2.8.3-respond-1.4.2.min.js

modernizr-2.8.3-respond-1.4.2.min.js

896 ms

jquery.min.js

jquery.min.js

72 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

757 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

928 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

763 ms

jquery-ui.min.js

jquery-ui.min.js

90 ms

jquery.ui.datepicker-ja.min.js

jquery.ui.datepicker-ja.min.js

83 ms

main-min.js

main-min.js

1037 ms

analytics.js

analytics.js

127 ms

2079a3ee7aa221853026eb00f2a869d8.png

2079a3ee7aa221853026eb00f2a869d8.png

692 ms

logo.png

logo.png

477 ms

budge-funded.png

budge-funded.png

477 ms

badge-the-day.png

badge-the-day.png

481 ms

budge-new.png

budge-new.png

473 ms

banner-jc.jpg

banner-jc.jpg

636 ms

banner-cs.jpg

banner-cs.jpg

478 ms

839.png

839.png

1293 ms

977.png

977.png

1014 ms

936.png

936.png

4485 ms

845.png

845.png

2139 ms

956.png

956.png

1658 ms

848.png

848.png

1058 ms

sdk.js

sdk.js

121 ms

991.png

991.png

1722 ms

884.png

884.png

1994 ms

1046.png

1046.png

3824 ms

945.png

945.png

1981 ms

1088.png

1088.png

4453 ms

1075.png

1075.png

2317 ms

1105.png

1105.png

2188 ms

1091.png

1091.png

2541 ms

1040.png

1040.png

2546 ms

1074.png

1074.png

2653 ms

1114.png

1114.png

3986 ms

1077.png

1077.png

2740 ms

1027.png

1027.png

3169 ms

1031.png

1031.png

2905 ms

994.png

994.png

3080 ms

1012.png

1012.png

3428 ms

eyecatch-img-0.png

eyecatch-img-0.png

875 ms

eyecatch-img-1.jpg

eyecatch-img-1.jpg

875 ms

eyecatch-img-2.jpg

eyecatch-img-2.jpg

873 ms

eyecatch-img-3.jpg

eyecatch-img-3.jpg

1034 ms

eyecatch-img-4.jpg

eyecatch-img-4.jpg

876 ms

eyecatch-img-5.png

eyecatch-img-5.png

1176 ms

eyecatch-img-6.jpg

eyecatch-img-6.jpg

1199 ms

eyecatch-img-7.png

eyecatch-img-7.png

1195 ms

eyecatch-img-8.jpg

eyecatch-img-8.jpg

1236 ms

pj-thumb-cover.png

pj-thumb-cover.png

1042 ms

area-bg.png

area-bg.png

1196 ms

start-pj.jpg

start-pj.jpg

1714 ms

icomoon.ttf

icomoon.ttf

1649 ms

collect

collect

41 ms

115 ms

xd_arbiter.php

xd_arbiter.php

54 ms

collect

collect

62 ms

ga-audiences

ga-audiences

39 ms

Accessibility Review

faavo.jp accessibility score

79

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.

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

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

High

Links do not have a discernible name

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

faavo.jp 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

Missing source maps for large first-party JavaScript

SEO Factors

faavo.jp SEO score

76

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faavo.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Faavo.jp 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

faavo.jp

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