7.9 sec in total
1.5 sec
5.7 sec
716 ms
Visit figgy.jp now to see the best up-to-date Figgy content for Japan and also check out these interesting facts you probably never knew about figgy.jp
人気フィギュアを豊富な画像や写真で紹介。欲しいフィギュアもまとめて簡単検索!人気フィギュアの注目ランキングも。新作おすすめフィギュアの発売日から予約情報まで、通販ショップ情報も掲載。アニメや特撮のフィギュア情報を扱うフィギュア総合情報サイトです。
Visit figgy.jpWe analyzed Figgy.jp page load time and found that the first response time was 1.5 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
figgy.jp performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value17.7 s
0/100
25%
Value11.9 s
4/100
10%
Value1,110 ms
23/100
30%
Value1.061
2/100
15%
Value18.5 s
3/100
10%
1452 ms
378 ms
388 ms
37 ms
898 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 52% of them (39 requests) were addressed to the original Figgy.jp, 9% (7 requests) were made to Ecx.images-amazon.com and 5% (4 requests) were made to Spdeliver.i-mobile.co.jp. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Figgy.jp.
Page size can be reduced by 374.5 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of Figgy.jp main page is 1.7 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 52.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. This page needs HTML code to be minified as it can gain 8.9 kB, which is 13% 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 52.4 kB or 79% of the original size.
Potential reduce by 157.0 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, Figgy needs image optimization as it can save up to 157.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 71.4 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 71.4 kB or 44% of the original size.
Potential reduce by 93.6 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. Figgy.jp needs all CSS files to be minified and compressed as it can save up to 93.6 kB or 86% of the original size.
Number of requests can be reduced by 24 (33%)
73
49
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Figgy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
figgy.jp
1452 ms
reset.css
378 ms
style.css
388 ms
jquery.min.js
37 ms
style_pc.css
898 ms
style_sp.css
758 ms
nendAdLoader.js
141 ms
ads.js
58 ms
bookmark_button.js
516 ms
ads.js
278 ms
bookmark_button.js
933 ms
platform.js
67 ms
line-button.js
581 ms
bg_pat.png
223 ms
sprite-sec38b3b12b.png
890 ms
i.jpg
536 ms
i.jpg
893 ms
i.jpg
935 ms
i.jpg
929 ms
i.jpg
625 ms
i.jpg
1255 ms
i.jpg
1736 ms
i.jpg
1792 ms
i.jpg
1073 ms
i.jpg
1295 ms
i.jpg
1301 ms
i.jpg
1599 ms
i.jpg
1611 ms
i.jpg
2030 ms
i.jpg
2031 ms
i.jpg
1949 ms
i.jpg
1972 ms
i.jpg
2770 ms
i.jpg
2509 ms
i.jpg
2749 ms
i.jpg
2331 ms
i.jpg
2864 ms
i.jpg
2594 ms
i.jpg
3123 ms
i.jpg
2940 ms
i.jpg
2976 ms
i.jpg
3652 ms
i.jpg
3139 ms
%E3%82%AA%E3%83%AA%E3%82%B8%E3%83%8A%E3%83%ABSNS%E3%83%9C%E3%82%BF%E3%83%B3%E3%81%AE%E7%94%BB%E5%83%8F
3064 ms
20120901_gamer.jpg
3119 ms
figgy.png
3346 ms
adcore.js
31 ms
adcore_pc.js
51 ms
adcore_pc_inline.js
50 ms
ad_spot.aspx
543 ms
396 ms
ads-common.js
260 ms
cm
247 ms
widgets.js
27 ms
sdk.js
283 ms
btn.js
88 ms
dc.js
62 ms
bgt
1844 ms
0.gif
338 ms
__utm.gif
12 ms
51-H+icTR1L._SY75_SX60_.jpg
40 ms
195 ms
51-1oROaEfL._SY75_SX60_.jpg
38 ms
51bvYlnrtlL._SY75_SX60_.jpg
32 ms
61TGhfx+p6L._SY75_SX60_.jpg
36 ms
61KuEKwqQWL._SY75_SX60_.jpg
30 ms
style.css
162 ms
ad_creative.ashx
468 ms
101 ms
xd_arbiter.php
235 ms
xd_arbiter.php
457 ms
51bvYlnrtlL._OU09_SL60_PI18-percent,BottomRight,0,0_CR0,0,60,34_.jpg
10 ms
61TGhfx+p6L._OU09_SL75_PI19-percent,BottomRight,0,0_CR0,0,60,75_.jpg
9 ms
error404.html
568 ms
RestoreXidToMediaStorage.html
46 ms
figgy.jp accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
figgy.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
figgy.jp SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Figgy.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 Figgy.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.
figgy.jp
Open Graph description is not detected on the main page of Figgy. 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: