Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

fuelphp.jp

FuelPHP.JP 日本語ドキュメント

Page Load Speed

2.3 sec in total

First Response

548 ms

Resources Loaded

1.6 sec

Page Rendered

97 ms

fuelphp.jp screenshot

About Website

Welcome to fuelphp.jp homepage info - get ready to check FuelPHP best content for Japan right away, or after learning these important things about fuelphp.jp

FuelPHP 日本語ドキュメントのトップページです

Visit fuelphp.jp

Key Findings

We analyzed Fuelphp.jp page load time and found that the first response time was 548 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

fuelphp.jp performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.7 s

100/100

10%

Network Requests Diagram

fuelphp.jp

548 ms

style.css

365 ms

reset.css

343 ms

ga.js

25 ms

drops.png

377 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 67% of them (4 requests) were addressed to the original Fuelphp.jp, 33% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (548 ms) belongs to the original domain Fuelphp.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.9 kB (24%)

Content Size

33.3 kB

After Optimization

25.4 kB

In fact, the total size of Fuelphp.jp main page is 33.3 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. Only 10% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 2.0 kB

  • Original 3.3 kB
  • After minification 2.9 kB
  • After compression 1.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. This page needs HTML code to be minified as it can gain 412 B, which is 12% 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 2.0 kB or 61% of the original size.

Image Optimization

-25%

Potential reduce by 1.8 kB

  • Original 7.0 kB
  • After minification 5.3 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. Obviously, FuelPHP needs image optimization as it can save up to 1.8 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

CSS Optimization

-70%

Potential reduce by 4.0 kB

  • Original 5.8 kB
  • After minification 4.7 kB
  • After compression 1.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. Fuelphp.jp needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 70% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FuelPHP. According to our analytics all requests are already optimized.

Accessibility Review

fuelphp.jp accessibility score

94

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

fuelphp.jp SEO score

94

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

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

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