Tools & Wizards About Us
ftj.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

ftj.jp

FINETECH JAPAN（電子ディスプレイ産業展）｜出展のご案内

Page Load Speed

3.1 sec in total

First Response

928 ms

Resources Loaded

1.8 sec

Page Rendered

366 ms

ftj.jp screenshot

About Website

Click here to check amazing Ftj content for Bangladesh. Otherwise, check out these important facts you probably never knew about ftj.jp

FPD業界 世界最大級の展示会、ファインテック ジャパン。最新のディスプレイ（液晶、有機EL、タッチパネルなど）から、製造装置、部品・材料まで、最先端技術が一堂に展示される専門技術展です。

Visit ftj.jp

Key Findings

We analyzed Ftj.jp page load time and found that the first response time was 928 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ftj.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value22.8 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value4,190 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.417

23/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

www.ftj.jp

928 ms

html5shiv.js

10 ms

NovaCss.x.css

22 ms

CustomNovaCss.x.css

30 ms

NovaJs.x.js

60 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 86% of them (85 requests) were addressed to the original Ftj.jp, 4% (4 requests) were made to Ad.doubleclick.net and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (928 ms) belongs to the original domain Ftj.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 413.4 kB (22%)

Content Size

1.9 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ftj.jp main page is 1.9 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 75.6 kB

  • Original 102.7 kB
  • After minification 89.6 kB
  • After compression 27.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. This page needs HTML code to be minified as it can gain 13.1 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 75.6 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 42.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB

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. Ftj images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 267.2 kB

  • Original 432.0 kB
  • After minification 425.2 kB
  • After compression 164.8 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 267.2 kB or 62% of the original size.

CSS Optimization

-85%

Potential reduce by 27.7 kB

  • Original 32.5 kB
  • After minification 23.7 kB
  • After compression 4.7 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. Ftj.jp needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (26%)

Requests Now

98

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ftj.jp

www.ftj.jp

928 ms

html5shiv.js

html5shiv.js

10 ms

NovaCss.x.css

NovaCss.x.css

22 ms

CustomNovaCss.x.css

CustomNovaCss.x.css

30 ms

NovaJs.x.js

NovaJs.x.js

60 ms

top_04.css

top_04.css

19 ms

jquery.bxslider01.css

jquery.bxslider01.css

17 ms

;Title=;kw=ceo_book;language=ja;sz=214x74;ord=1058820019

;Title=;kw=ceo_book;language=ja;sz=214x74;ord=1058820019

49 ms

;Title=;kw=reed_top53;language=ja;sz=212x74;ord=1058820019

;Title=;kw=reed_top53;language=ja;sz=212x74;ord=1058820019

48 ms

;Title=;kw=RXJP_top_E_blue;language=ja;sz=340x74;ord=1058820019

;Title=;kw=RXJP_top_E_blue;language=ja;sz=340x74;ord=1058820019

50 ms

;Title=;kw=yokosojapan-jp%20and%20yokosojapan-en;language=ja;sz=104x74;ord=1058820019

;Title=;kw=yokosojapan-jp%20and%20yokosojapan-en;language=ja;sz=104x74;ord=1058820019

48 ms

iPad.js

iPad.js

47 ms

analytics.js

analytics.js

116 ms

13855675261481430038

13855675261481430038

93 ms

addthis_widget.js

addthis_widget.js

38 ms

17170908880504218980

17170908880504218980

12 ms

13564457623509879338

13564457623509879338

13 ms

body_bg01.gif

body_bg01.gif

14 ms

wrapper_topbar_bg01.gif

wrapper_topbar_bg01.gif

87 ms

header_bg01.gif

header_bg01.gif

88 ms

FTJ_logo.png

FTJ_logo.png

106 ms

space.gif

space.gif

88 ms

BG_search.gif

BG_search.gif

87 ms

topNavigation_bg02.gif

topNavigation_bg02.gif

88 ms

topNavigation_level1-boder01.gif

topNavigation_level1-boder01.gif

89 ms

img_slide01.jpg

img_slide01.jpg

91 ms

img_slide02.jpg

img_slide02.jpg

111 ms

img_slide03.jpg

img_slide03.jpg

90 ms

ic_h2.gif

ic_h2.gif

113 ms

bg_pickup.gif

bg_pickup.gif

120 ms

ico_new.gif

ico_new.gif

167 ms

ico_blank.gif

ico_blank.gif

169 ms

ic_detail.png

ic_detail.png

201 ms

img_pickup_inv.jpg

img_pickup_inv.jpg

141 ms

img_pickup_vip.jpg

img_pickup_vip.jpg

129 ms

ic-ftjk.png

ic-ftjk.png

128 ms

list.gif

list.gif

137 ms

ic_translation_3.png

ic_translation_3.png

156 ms

FTJ-K_1.jpg

FTJ-K_1.jpg

146 ms

FTJ-K_2.jpg

FTJ-K_2.jpg

149 ms

FTJ-K_3.jpg

FTJ-K_3.jpg

156 ms

img_pickup_photogallery.jpg

img_pickup_photogallery.jpg

159 ms

film_logo_s.gif

film_logo_s.gif

166 ms

pla_logo_s.gif

pla_logo_s.gif

254 ms

metal_logo_s.gif

metal_logo_s.gif

169 ms

cera_logo_s.gif

cera_logo_s.gif

175 ms

photo_logo_s.gif

photo_logo_s.gif

174 ms

ftjjp_16_committeeph_01re2.jpg

ftjjp_16_committeeph_01re2.jpg

172 ms

ftjjp_16_committeeph_02.jpg

ftjjp_16_committeeph_02.jpg

178 ms

ftjjp_16_committeeph_03.JPG

ftjjp_16_committeeph_03.JPG

181 ms

ftjjp_16_committeeph_04.jpg

ftjjp_16_committeeph_04.jpg

183 ms

ftjjp_16_committeeph_05.jpg

ftjjp_16_committeeph_05.jpg

184 ms

ftjjp_16_committeeph_06.JPG

ftjjp_16_committeeph_06.JPG

185 ms

collect

collect

64 ms

collect

collect

18 ms

collect

collect

19 ms

ftjjp_16_committeeph_07.jpg

ftjjp_16_committeeph_07.jpg

110 ms

ftjjp_16_committeeph_08.jpg

ftjjp_16_committeeph_08.jpg

109 ms

ftjjp_16_committeeph_09.jpg

ftjjp_16_committeeph_09.jpg

110 ms

ftjjp_16_committeeph_10.jpg

ftjjp_16_committeeph_10.jpg

109 ms

ftjjp_16_committeeph_11.JPG

ftjjp_16_committeeph_11.JPG

112 ms

ftjjp_16_committeeph_12.JPG

ftjjp_16_committeeph_12.JPG

116 ms

ftjjp_16_committeeph_13.jpg

ftjjp_16_committeeph_13.jpg

117 ms

ftjjp_16_committeeph_14.jpg

ftjjp_16_committeeph_14.jpg

117 ms

e-flyinc.jpg

e-flyinc.jpg

109 ms

banner_se_2015_prepare.png

banner_se_2015_prepare.png

126 ms

banner_se_2015_step01.png

banner_se_2015_step01.png

117 ms

ftjjp_rightrcolumn_bnr_01.gif

ftjjp_rightrcolumn_bnr_01.gif

130 ms

banner_se_2015_arrow.png

banner_se_2015_arrow.png

163 ms

banner_se_2015_step02.png

banner_se_2015_step02.png

109 ms

banner_se_2015_step02_btn.gif

banner_se_2015_step02_btn.gif

111 ms

banner_se_2015_step03.png

banner_se_2015_step03.png

102 ms

banner_se_2015_step03_btn.gif

banner_se_2015_step03_btn.gif

105 ms

banner_se_2015_step04.png

banner_se_2015_step04.png

101 ms

banner_se_2015_step04_btn.gif

banner_se_2015_step04_btn.gif

97 ms

banner_se_2015_QandA.gif

banner_se_2015_QandA.gif

92 ms

banner_se_2015_VIP.gif

banner_se_2015_VIP.gif

102 ms

footer_bg01.gif

footer_bg01.gif

113 ms

footer_bg.gif

footer_bg.gif

89 ms

ft_logo.png

ft_logo.png

158 ms

reed_logo.png

reed_logo.png

93 ms

ft_visit.png

ft_visit.png

125 ms

ft_visit_tel.png

ft_visit_tel.png

117 ms

ft_visit_mail.png

ft_visit_mail.png

101 ms

bnr_inv.gif

bnr_inv.gif

105 ms

ft_exhibit.png

ft_exhibit.png

107 ms

ft_exhibit_tel.png

ft_exhibit_tel.png

105 ms

ft_exhibit_mail.png

ft_exhibit_mail.png

106 ms

bnr_ex.gif

bnr_ex.gif

123 ms

White-TM.png

White-TM.png

107 ms

separate_top.gif

separate_top.gif

107 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

108 ms

ic_pg.png

ic_pg.png

197 ms

btn_slide_prev.png

btn_slide_prev.png

209 ms

btn_slide_next.png

btn_slide_next.png

188 ms

ic_pg_active.png

ic_pg_active.png

190 ms

uab.js

uab.js

25 ms

300lo.json

300lo.json

34 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

28 ms

Accessibility Review

ftj.jp accessibility score

95

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

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

ftj.jp SEO score

88

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

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

ftj.jp

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