Report Summary

  • 45

    Performance

    Renders faster than
    65% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

freeing.co.jp

FREEing

Page Load Speed

1.8 sec in total

First Response

549 ms

Resources Loaded

1.2 sec

Page Rendered

105 ms

freeing.co.jp screenshot

About Website

Visit freeing.co.jp now to see the best up-to-date FREEing content for Taiwan and also check out these interesting facts you probably never knew about freeing.co.jp

フィギュア製造のFREEing

Visit freeing.co.jp

Key Findings

We analyzed Freeing.co.jp page load time and found that the first response time was 549 ms and then it took 1.3 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

freeing.co.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value7.2 s

29/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

freeing.co.jp

549 ms

swfobject.js

174 ms

swffit.js

321 ms

index_old.php

388 ms

ga.js

40 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 63% of them (5 requests) were addressed to the original Freeing.co.jp, 25% (2 requests) were made to Google-analytics.com and 13% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (549 ms) belongs to the original domain Freeing.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.6 kB (20%)

Content Size

53.6 kB

After Optimization

43.0 kB

In fact, the total size of Freeing.co.jp main page is 53.6 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 5% of websites need less resources to load. Javascripts take 30.6 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 1.4 kB

  • Original 2.8 kB
  • After minification 2.7 kB
  • After compression 1.4 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 1.4 kB or 50% of the original size.

Image Optimization

-4%

Potential reduce by 821 B

  • Original 20.2 kB
  • After minification 19.4 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. FREEing images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 8.4 kB

  • Original 30.6 kB
  • After minification 30.3 kB
  • After compression 22.3 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 8.4 kB or 27% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

7

After Optimization

7

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

Accessibility Review

freeing.co.jp accessibility score

82

Accessibility Issues

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

freeing.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

freeing.co.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freeing.co.jp 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 Freeing.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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