Tools & Wizards About Us
fjtex.co.jp screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

fjtex.co.jp

株式会社フジテックス

Page Load Speed

2.2 sec in total

First Response

413 ms

Resources Loaded

1.6 sec

Page Rendered

183 ms

fjtex.co.jp screenshot

About Website

Click here to check amazing Fjtex content for Japan. Otherwise, check out these important facts you probably never knew about fjtex.co.jp

株式会社フジテックスは、販促事業、環境事業、健康事業、教育事業からなる総合商社です。フジテックスはこの4事業を通じて、お客様により良い製品を提供してまいります。

Visit fjtex.co.jp

Key Findings

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

fjtex.co.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

fjtex.co.jp

413 ms

common.css

159 ms

smartRollover.js

377 ms

scrollsmoothly.js

398 ms

ga.js

38 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Fjtex.co.jp, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fjtex.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.1 kB (10%)

Content Size

412.3 kB

After Optimization

370.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 11.3 kB

  • Original 15.5 kB
  • After minification 15.2 kB
  • After compression 4.2 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 11.3 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 12.5 kB

  • Original 357.0 kB
  • After minification 344.5 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. Fjtex images are well optimized though.

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

-81%

Potential reduce by 18.2 kB

  • Original 22.6 kB
  • After minification 18.9 kB
  • After compression 4.4 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. Fjtex.co.jp needs all CSS files to be minified and compressed as it can save up to 18.2 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

38

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fjtex.co.jp

fjtex.co.jp

413 ms

common.css

common.css

159 ms

smartRollover.js

smartRollover.js

377 ms

scrollsmoothly.js

scrollsmoothly.js

398 ms

ga.js

ga.js

38 ms

hnav_eng_index.gif

hnav_eng_index.gif

293 ms

hnav_sitemap_index.gif

hnav_sitemap_index.gif

295 ms

btn_more.gif

btn_more.gif

315 ms

relaese_topics.gif

relaese_topics.gif

316 ms

relaese_products.gif

relaese_products.gif

348 ms

relaese_press.gif

relaese_press.gif

382 ms

btn_serch.gif

btn_serch.gif

461 ms

pagetop.gif

pagetop.gif

460 ms

footnav_cont.gif

footnav_cont.gif

471 ms

footnav_sitemap.gif

footnav_sitemap.gif

470 ms

footnav_eng.gif

footnav_eng.gif

493 ms

foot_logo.gif

foot_logo.gif

536 ms

copyright.gif

copyright.gif

606 ms

bg_index.png

bg_index.png

315 ms

bg_head_index.png

bg_head_index.png

1056 ms

h1_best.png

h1_best.png

456 ms

gnav.png

gnav.png

294 ms

bg_wrap.jpg

bg_wrap.jpg

296 ms

bg_cont.jpg

bg_cont.jpg

300 ms

bg_h2.gif

bg_h2.gif

460 ms

h2_release.gif

h2_release.gif

459 ms

bg_serch.gif

bg_serch.gif

462 ms

bg_serch_txt.gif

bg_serch_txt.gif

469 ms

bnr_env.jpg

bnr_env.jpg

601 ms

bnr_sales.jpg

bnr_sales.jpg

609 ms

bnr_snk.jpg

bnr_snk.jpg

609 ms

bnr_kbc.jpg

bnr_kbc.jpg

610 ms

bnr_bhc.jpg

bnr_bhc.jpg

645 ms

bnr_log.jpg

bnr_log.jpg

748 ms

bnr_recruit2017.jpg

bnr_recruit2017.jpg

750 ms

bg_foot.gif

bg_foot.gif

752 ms

icon_blank.gif

icon_blank.gif

781 ms

bg_foot_index.gif

bg_foot_index.gif

802 ms

__utm.gif

__utm.gif

11 ms

309 ms

Accessibility Review

fjtex.co.jp accessibility score

92

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.

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

fjtex.co.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fjtex.co.jp SEO score

97

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fjtex.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 Fjtex.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

fjtex.co.jp

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