Tools & Wizards About Us
fjx.co.jp screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

fjx.co.jp

高機能で色数豊富な高品質糸を扱う株式会社フジックス

Page Load Speed

6.2 sec in total

First Response

519 ms

Resources Loaded

5.4 sec

Page Rendered

263 ms

fjx.co.jp screenshot

About Website

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

株式会社フジックスでは、高機能で高品質なミシン糸・手縫い糸・刺繍糸を、色数豊富に取り揃えています。また、用途も工業用糸から家庭用糸まで全てのカテゴリーでご活用していただけます。

Visit fjx.co.jp

Key Findings

We analyzed Fjx.co.jp page load time and found that the first response time was 519 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fjx.co.jp performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.167

71/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

fjx.co.jp

519 ms

fjx.co.jp

907 ms

js

71 ms

js

153 ms

import.css

194 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 79% of them (77 requests) were addressed to the original Fjx.co.jp, 4% (4 requests) were made to Googletagmanager.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fjx.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.3 kB (36%)

Content Size

1.1 MB

After Optimization

709.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fjx.co.jp main page is 1.1 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. 55% of websites need less resources to load. Images take 610.2 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 31.8 kB

  • Original 39.2 kB
  • After minification 29.8 kB
  • After compression 7.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 9.4 kB, which is 24% 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 31.8 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 15.5 kB

  • Original 610.2 kB
  • After minification 594.7 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. Fjx images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 312.7 kB

  • Original 410.7 kB
  • After minification 275.2 kB
  • After compression 98.0 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 312.7 kB or 76% of the original size.

CSS Optimization

-83%

Potential reduce by 46.3 kB

  • Original 55.9 kB
  • After minification 39.6 kB
  • After compression 9.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. Fjx.co.jp needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (34%)

Requests Now

95

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fjx.co.jp

fjx.co.jp

519 ms

fjx.co.jp

fjx.co.jp

907 ms

js

js

71 ms

js

js

153 ms

import.css

import.css

194 ms

uniq.css

uniq.css

354 ms

fontsize.css

fontsize.css

521 ms

import.js

import.js

527 ms

line_height.js

line_height.js

526 ms

xj.css

xj.css

529 ms

XjStorageLoaderTopNews.js

XjStorageLoaderTopNews.js

365 ms

js

js

45 ms

js

js

47 ms

analytics.js

analytics.js

21 ms

normalize.css

normalize.css

336 ms

base.css

base.css

482 ms

component.css

component.css

666 ms

collect

collect

59 ms

collect

collect

29 ms

default.js

default.js

177 ms

innerlink.js

innerlink.js

181 ms

jquery.js

jquery.js

1024 ms

jquery.autoHeight.js

jquery.autoHeight.js

179 ms

jquery.opacity-rollover.js

jquery.opacity-rollover.js

174 ms

jquery_scrolltop.js

jquery_scrolltop.js

176 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

346 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

350 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

351 ms

jquery.biggerlink.min.js

jquery.biggerlink.min.js

358 ms

jquery.parts.js

jquery.parts.js

361 ms

googleanalytics.js

googleanalytics.js

518 ms

jquery.socialbutton-1.9.1.js

jquery.socialbutton-1.9.1.js

524 ms

ga.js

ga.js

142 ms

bg_top.jpg

bg_top.jpg

778 ms

bg_header.png

bg_header.png

274 ms

icon_tri.png

icon_tri.png

270 ms

icon_cart.png

icon_cart.png

272 ms

icon_mail.png

icon_mail.png

268 ms

logo_side.gif

logo_side.gif

269 ms

gNav_01.gif

gNav_01.gif

440 ms

line_02.png

line_02.png

443 ms

icon_tri_02.png

icon_tri_02.png

444 ms

gNav_02.gif

gNav_02.gif

448 ms

gNav_04.gif

gNav_04.gif

451 ms

icon_window.png

icon_window.png

613 ms

icon_gNav03.png

icon_gNav03.png

618 ms

gNav_03.gif

gNav_03.gif

617 ms

gNav_05.gif

gNav_05.gif

624 ms

gNav_06.gif

gNav_06.gif

631 ms

gNav_07.gif

gNav_07.gif

786 ms

bg_sns.gif

bg_sns.gif

792 ms

icon_tw.gif

icon_tw.gif

792 ms

icon_insta.gif

icon_insta.gif

799 ms

bnr_schappespun_50th.jpg

bnr_schappespun_50th.jpg

809 ms

bnr_side_03.jpg

bnr_side_03.jpg

948 ms

bnr_side_09.jpg

bnr_side_09.jpg

957 ms

bnr_side_07.gif

bnr_side_07.gif

966 ms

bnr_itotasu.jpg

bnr_itotasu.jpg

967 ms

bnr_side_04.jpg

bnr_side_04.jpg

1145 ms

bnr_side_11.jpg

bnr_side_11.jpg

986 ms

bnr_side_08.gif

bnr_side_08.gif

1122 ms

bnr_side_15.jpg

bnr_side_15.jpg

1129 ms

bnr_side_13.jpg

bnr_side_13.jpg

1140 ms

tx_mv.png

tx_mv.png

1311 ms

btn_list.png

btn_list.png

1169 ms

line_03.png

line_03.png

1296 ms

icon_news_04.gif

icon_news_04.gif

1301 ms

icon_new.gif

icon_new.gif

1314 ms

widgets.js

widgets.js

90 ms

like.php

like.php

456 ms

GetList.aspx

GetList.aspx

382 ms

icon_news_02.gif

icon_news_02.gif

1203 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

settings

settings

99 ms

bg_topBnr.png

bg_topBnr.png

1091 ms

bnr_index_01.jpg

bnr_index_01.jpg

1210 ms

bnr_index_02.jpg

bnr_index_02.jpg

1213 ms

bnr_index_03.jpg

bnr_index_03.jpg

1222 ms

h_index_01.gif

h_index_01.gif

1226 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

22 ms

embeds

embeds

36 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

32 ms

img_index_01.jpg

img_index_01.jpg

1067 ms

img_index_02.jpg

img_index_02.jpg

1097 ms

img_index_03.jpg

img_index_03.jpg

1210 ms

img_index_04.jpg

img_index_04.jpg

1208 ms

bg_footer_top.jpg

bg_footer_top.jpg

1217 ms

9RkfBY4NJsx.js

9RkfBY4NJsx.js

24 ms

FEppCFCt76d.png

FEppCFCt76d.png

12 ms

icon_tri_03.png

icon_tri_03.png

1056 ms

bg_foooter_bottom.gif

bg_foooter_bottom.gif

1067 ms

logo_footer.png

logo_footer.png

1104 ms

scrollup.png

scrollup.png

1204 ms

icon_news_01.gif

icon_news_01.gif

1198 ms

icon_pdf.png

icon_pdf.png

1069 ms

print.css

print.css

177 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

fjx.co.jp accessibility score

82

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

Links do not have a discernible name

Best Practices

fjx.co.jp best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fjx.co.jp SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Fjx.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 Fjx.co.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

fjx.co.jp

Open Graph data is detected on the main page of Fjx. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: