Tools & Wizards About Us
j-texts.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

j-texts.com

養育費未払相談所 | 養育費未払い問題の相談窓口

Page Load Speed

4.1 sec in total

First Response

821 ms

Resources Loaded

3.1 sec

Page Rendered

182 ms

j-texts.com screenshot

About Website

Welcome to j-texts.com homepage info - get ready to check J Texts best content for Japan right away, or after learning these important things about j-texts.com

日本文学関係のテキストアーカイブ（電子図書館）Ｊ－ＴＥＸＴＳ

Visit j-texts.com

Key Findings

We analyzed J-texts.com page load time and found that the first response time was 821 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

j-texts.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.136

80/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

j-texts.com

821 ms

jtsmain.gif

386 ms

show_ads.js

11 ms

brand

50 ms

ca-pub-6698281641507638.js

59 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original J-texts.com, 13% (13 requests) were made to Cdn.flashtalking.com and 13% (13 requests) were made to Secure.flashtalking.com. The less responsive or slowest element that took the longest time to load (821 ms) belongs to the original domain J-texts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.8 kB (63%)

Content Size

491.7 kB

After Optimization

179.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of J-texts.com main page is 491.7 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. 45% of websites need less resources to load. Javascripts take 434.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 16.3 kB

  • Original 21.9 kB
  • After minification 21.7 kB
  • After compression 5.5 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 16.3 kB or 75% of the original size.

Image Optimization

-10%

Potential reduce by 3.0 kB

  • Original 31.6 kB
  • After minification 28.6 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. J Texts images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 289.6 kB

  • Original 434.2 kB
  • After minification 412.5 kB
  • After compression 144.6 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 289.6 kB or 67% of the original size.

CSS Optimization

-70%

Potential reduce by 2.8 kB

  • Original 4.0 kB
  • After minification 2.9 kB
  • After compression 1.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. J-texts.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (67%)

Requests Now

88

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

j-texts.com

j-texts.com

821 ms

jtsmain.gif

jtsmain.gif

386 ms

show_ads.js

show_ads.js

11 ms

brand

brand

50 ms

ca-pub-6698281641507638.js

ca-pub-6698281641507638.js

59 ms

zrt_lookup.html

zrt_lookup.html

43 ms

show_ads_impl.js

show_ads_impl.js

63 ms

brand

brand

33 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

129 ms

ads

ads

230 ms

osd.js

osd.js

26 ms

cm

cm

209 ms

ads

ads

215 ms

0656415

0656415

561 ms

Logo_40wht.gif

Logo_40wht.gif

259 ms

icon-1.gif

icon-1.gif

375 ms

icon-2.gif

icon-2.gif

385 ms

jts8831.gif

jts8831.gif

386 ms

arayama.gif

arayama.gif

404 ms

assoc728x90_crocs_0424.png

assoc728x90_crocs_0424.png

27 ms

187 ms

m_js_controller.js

m_js_controller.js

41 ms

abg.js

abg.js

64 ms

162 ms

adj

adj

118 ms

beacon

beacon

100 ms

favicon

favicon

59 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

46 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

37 ms

s

s

23 ms

x_button_blue2.png

x_button_blue2.png

10 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

3 ms

32 ms

0

0

55 ms

surly.js

surly.js

75 ms

320 ms

verify_selector.js

verify_selector.js

193 ms

blank.gif

blank.gif

191 ms

ba.html

ba.html

16 ms

pixel

pixel

16 ms

lidar.js

lidar.js

15 ms

sbhK2lTE.js

sbhK2lTE.js

13 ms

4.gif

4.gif

34 ms

pixel

pixel

94 ms

pixel

pixel

96 ms

4311.js

4311.js

65 ms

cTrvNaRi.html

cTrvNaRi.html

24 ms

0656415

0656415

620 ms

sd

sd

27 ms

sc.bci

sc.bci

94 ms

j-1734608-1324496.js

j-1734608-1324496.js

38 ms

index.html

index.html

23 ms

dvtp_src.js

dvtp_src.js

33 ms

verifyr.js

verifyr.js

47 ms

style.css

style.css

11 ms

html5API.js

html5API.js

232 ms

library.js

library.js

16 ms

main.js

main.js

32 ms

css

css

244 ms

dvtp_src_internal26.js

dvtp_src_internal26.js

20 ms

beacon.js

beacon.js

191 ms

0

0

176 ms

bg.png

bg.png

182 ms

adchoices.en.png

adchoices.en.png

285 ms

t2tv7.html

t2tv7.html

299 ms

visit.js

visit.js

198 ms

i_btn_redeem.gif

i_btn_redeem.gif

148 ms

i_btn_zip.gif

i_btn_zip.gif

68 ms

manifest.js

manifest.js

99 ms

i_bg.jpg

i_bg.jpg

70 ms

i_discount.png

i_discount.png

70 ms

i_logo.png

i_logo.png

71 ms

i_separator.png

i_separator.png

70 ms

1TiHc9yag0wq3lDO9cw0viZ2oysoEQEeKwjgmXLRnTc.ttf

1TiHc9yag0wq3lDO9cw0viZ2oysoEQEeKwjgmXLRnTc.ttf

69 ms

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

mUangSEE-PUZJVLGz-Lt6-vvDin1pK8aKteLpeZ5c0A.ttf

85 ms

avs581.js

avs581.js

26 ms

trac.js

trac.js

364 ms

Logo_40wht.gif

Logo_40wht.gif

178 ms

0656415

0656415

388 ms

event.jpg

event.jpg

45 ms

1324496.json

1324496.json

13 ms

storelocator.js

storelocator.js

9 ms

list.js

list.js

33 ms

box_19_top-right.png

box_19_top-right.png

37 ms

ci.png

ci.png

47 ms

984.js

984.js

28 ms

163.js

163.js

37 ms

982.js

982.js

40 ms

811.js

811.js

39 ms

13.js

13.js

55 ms

249.js

249.js

99 ms

773.js

773.js

37 ms

222.js

222.js

35 ms

397.js

397.js

45 ms

366.js

366.js

50 ms

activeview

activeview

13 ms

cookiesync

cookiesync

380 ms

Accessibility Review

j-texts.com accessibility score

98

Accessibility Issues

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

j-texts.com 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

j-texts.com SEO score

86

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise J-texts.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that J-texts.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

j-texts.com

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