Tools & Wizards About Us
figsoku.net screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

figsoku.net

fig速-フィギュア・プラモ 新作ホビー情報まとめ

Page Load Speed

4.9 sec in total

First Response

1.1 sec

Resources Loaded

3.5 sec

Page Rendered

322 ms

figsoku.net screenshot

About Website

Welcome to figsoku.net homepage info - get ready to check Figsoku best content for Japan right away, or after learning these important things about figsoku.net

フィギュアやガンプラほか新作ホビー情報ブログ、ワンフェスなどのイベント記事も掲載しています

Visit figsoku.net

Key Findings

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

Performance Metrics

figsoku.net performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value250 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.445

21/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

figsoku.net

1053 ms

jquery.min.js

20 ms

style.css

211 ms

f.js

82 ms

f.js

83 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 43% of them (17 requests) were addressed to the original Figsoku.net, 10% (4 requests) were made to Rss.solty.biz and 8% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Figsoku.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 57.7 kB (7%)

Content Size

877.4 kB

After Optimization

819.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 39.4 kB

  • Original 49.5 kB
  • After minification 47.0 kB
  • After compression 10.1 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 39.4 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 13.6 kB

  • Original 776.8 kB
  • After minification 763.2 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. Figsoku images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 298 B

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

CSS Optimization

-38%

Potential reduce by 4.4 kB

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 7.2 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. Figsoku.net needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 38% 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 Figsoku. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

figsoku.net

figsoku.net

1053 ms

jquery.min.js

jquery.min.js

20 ms

style.css

style.css

211 ms

f.js

f.js

82 ms

f.js

f.js

83 ms

main.min.js

main.min.js

418 ms

js

js

79 ms

all.min.css

all.min.css

44 ms

figrss.html

figrss.html

445 ms

header.png

header.png

629 ms

sh.adingo.jp

sh.adingo.jp

646 ms

FIGURE-171728.jpg

FIGURE-171728.jpg

743 ms

FIGURE-167751.jpg

FIGURE-167751.jpg

1276 ms

FIGURE-167710.jpg

FIGURE-167710.jpg

1288 ms

icon_rss.png

icon_rss.png

288 ms

202407020118131.jpg

202407020118131.jpg

1110 ms

202405090100421-200x150.jpg

202405090100421-200x150.jpg

881 ms

202407090342581-200x150.jpg

202407090342581-200x150.jpg

882 ms

202407090319461-200x150.jpg

202407090319461-200x150.jpg

882 ms

202407090301591-200x150.jpg

202407090301591-200x150.jpg

883 ms

202407090303161-200x150.jpg

202407090303161-200x150.jpg

953 ms

202407090300551-200x150.jpg

202407090300551-200x150.jpg

1060 ms

202407090318361-200x150.jpg

202407090318361-200x150.jpg

1061 ms

202407090305551-200x150.jpg

202407090305551-200x150.jpg

1067 ms

202407050243451.jpg

202407050243451.jpg

1919 ms

48.js

48.js

504 ms

13.js

13.js

507 ms

14.js

14.js

558 ms

15.js

15.js

560 ms

j

j

449 ms

i.adingo.jp

i.adingo.jp

639 ms

sh.adingo.jp

sh.adingo.jp

179 ms

adroute_ads.js

adroute_ads.js

197 ms

i.adingo.jp

i.adingo.jp

612 ms

202404030617571.jpg

202404030617571.jpg

822 ms

fa-solid-900.woff

fa-solid-900.woff

13 ms

fa-regular-400.woff

fa-regular-400.woff

25 ms

show_page.html

show_page.html

1177 ms

v1

v1

633 ms

23815_15550514811422.jpg

23815_15550514811422.jpg

5 ms

Accessibility Review

figsoku.net accessibility score

69

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

figsoku.net SEO score

91

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

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 uses 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 Figsoku.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 Figsoku.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

figsoku.net

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