Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

fooline.net

FOOLINE(フーリネ)

Page Load Speed

10.4 sec in total

First Response

2.2 sec

Resources Loaded

7.7 sec

Page Rendered

493 ms

fooline.net screenshot

About Website

Click here to check amazing FOOLINE content for Japan. Otherwise, check out these important facts you probably never knew about fooline.net

ビジネスやカルチャーなど、様々なテーマで情報をお届けするコラムサイト。

Visit fooline.net

Key Findings

We analyzed Fooline.net page load time and found that the first response time was 2.2 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fooline.net performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value2,450 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.046

99/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

fooline.net

2212 ms

analytics.js

27 ms

wp-emoji-release.min.js

165 ms

crayon.min.css

319 ms

classic.css

342 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 52% of them (49 requests) were addressed to the original Fooline.net, 13% (12 requests) were made to Adm.shinobi.jp and 5% (5 requests) were made to Ssp.advg.jp. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fooline.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 424.7 kB (33%)

Content Size

1.3 MB

After Optimization

863.3 kB

In fact, the total size of Fooline.net main page is 1.3 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. 40% of websites need less resources to load. Images take 682.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 41.5 kB

  • Original 50.9 kB
  • After minification 46.6 kB
  • After compression 9.3 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 41.5 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 682.1 kB
  • After minification 682.1 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. FOOLINE images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 257.9 kB

  • Original 403.9 kB
  • After minification 400.3 kB
  • After compression 146.1 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 257.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 125.3 kB

  • Original 151.1 kB
  • After minification 123.3 kB
  • After compression 25.8 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. Fooline.net needs all CSS files to be minified and compressed as it can save up to 125.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

88

After Optimization

35

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

Accessibility Review

fooline.net accessibility score

82

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

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fooline.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fooline.net SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fooline.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Fooline.net 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 description is not detected on the main page of FOOLINE. 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: