Tools & Wizards About Us
ozeki.fa-fa.com screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

ozeki.fa-fa.com

エックスサーバー サーバー初期ページ

Page Load Speed

37.9 sec in total

First Response

1.3 sec

Resources Loaded

33.2 sec

Page Rendered

3.3 sec

ozeki.fa-fa.com screenshot

About Website

Visit ozeki.fa-fa.com now to see the best up-to-date Ozeki Fa content for Japan and also check out these interesting facts you probably never knew about ozeki.fa-fa.com

去年から近しい人の死が続いておりました。母と仲の良かった叔母と、そして母の忌明けとなりました。いつも気を使ってばかりの母は、自分のことよりも人のことを心配してばかりの人生だったように感じます。祖母と同じく、いつも大袈裟に心配したり話したりし

Visit ozeki.fa-fa.com

Key Findings

We analyzed Ozeki.fa-fa.com page load time and found that the first response time was 1.3 sec and then it took 36.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ozeki.fa-fa.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

ozeki.fa-fa.com

1301 ms

jm_style.css

504 ms

style.css

259 ms

cookie.js

462 ms

script.js

259 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 9% of them (13 requests) were addressed to the original Ozeki.fa-fa.com, 18% (26 requests) were made to Static.xx.fbcdn.net and 17% (24 requests) were made to Imaging.jugem.jp. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Go2web20.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.3 kB (58%)

Content Size

352.7 kB

After Optimization

148.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ozeki.fa-fa.com main page is 352.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 269.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.3 kB

  • Original 36.6 kB
  • After minification 34.5 kB
  • After compression 9.3 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 27.3 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 3.2 kB

  • Original 28.5 kB
  • After minification 25.3 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, Ozeki Fa needs image optimization as it can save up to 3.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 159.9 kB

  • Original 269.4 kB
  • After minification 237.7 kB
  • After compression 109.5 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 159.9 kB or 59% of the original size.

CSS Optimization

-76%

Potential reduce by 13.9 kB

  • Original 18.2 kB
  • After minification 14.6 kB
  • After compression 4.3 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. Ozeki.fa-fa.com needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 88 (68%)

Requests Now

130

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ozeki.fa-fa.com

ozeki.fa-fa.com

1301 ms

jm_style.css

jm_style.css

504 ms

style.css

style.css

259 ms

cookie.js

cookie.js

462 ms

script.js

script.js

259 ms

badge.js

badge.js

20238 ms

jquery.min.js

jquery.min.js

129 ms

metallica.css

metallica.css

256 ms

metallica.js

metallica.js

257 ms

fav.js

fav.js

254 ms

fav.css

fav.css

255 ms

login_popup.css

login_popup.css

279 ms

widgets.js

widgets.js

234 ms

show_ads.js

show_ads.js

68 ms

article.js

article.js

714 ms

cookie.js

cookie.js

73 ms

ga.js

ga.js

243 ms

back.gif

back.gif

294 ms

line1.jpg

line1.jpg

294 ms

line3.gif

line3.gif

294 ms

line2.jpg

line2.jpg

435 ms

calendar_head.gif

calendar_head.gif

437 ms

list.gif

list.gif

456 ms

ozeki.fa-fa.com

ozeki.fa-fa.com

580 ms

powered_07b.gif

powered_07b.gif

466 ms

bg_header.gif

bg_header.gif

66 ms

logo_jugem.gif

logo_jugem.gif

67 ms

bg_dot.gif

bg_dot.gif

67 ms

logo_pepabo.gif

logo_pepabo.gif

68 ms

left.gif

left.gif

460 ms

header.jpg

header.jpg

657 ms

__utm.gif

__utm.gif

82 ms

back.gif

back.gif

926 ms

line1.jpg

line1.jpg

82 ms

line3.gif

line3.gif

90 ms

line2.jpg

line2.jpg

1115 ms

calendar_head.gif

calendar_head.gif

124 ms

list.gif

list.gif

97 ms

powered_07b.gif

powered_07b.gif

73 ms

left.gif

left.gif

1053 ms

header.jpg

header.jpg

900 ms

add_heart.gif

add_heart.gif

91 ms

add_bubble.gif

add_bubble.gif

89 ms

lovewindow_b.gif

lovewindow_b.gif

89 ms

sdk.js

sdk.js

18 ms

widget.zenback.jp

widget.zenback.jp

333 ms

199 ms

xd_arbiter.php

xd_arbiter.php

158 ms

xd_arbiter.php

xd_arbiter.php

206 ms

jquery.min.js

jquery.min.js

556 ms

tracking.html

tracking.html

342 ms

ca-pub-6859523133129815.js

ca-pub-6859523133129815.js

497 ms

zrt_lookup.html

zrt_lookup.html

500 ms

show_ads_impl.js

show_ads_impl.js

253 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

529 ms

widget.zenback.jp

widget.zenback.jp

243 ms

dc.js

dc.js

217 ms

ads

ads

250 ms

osd.js

osd.js

116 ms

share_button.php

share_button.php

220 ms

__utm.gif

__utm.gif

168 ms

__utm.gif

__utm.gif

155 ms

button-only.gif

button-only.gif

593 ms

article-clipper-jp.png

article-clipper-jp.png

139 ms

article-no-image16x16.png

article-no-image16x16.png

415 ms

bookmark_button.js

bookmark_button.js

542 ms

plusone.js

plusone.js

378 ms

all.js

all.js

174 ms

noteit.js

noteit.js

358 ms

share.js

share.js

534 ms

lift_widget.js

lift_widget.js

733 ms

article-no-image16x16_out.png

article-no-image16x16_out.png

486 ms

poweredby.png

poweredby.png

486 ms

icon-oshirase.png

icon-oshirase.png

698 ms

icon-relatedentry.png

icon-relatedentry.png

700 ms

icon-relatedlink.png

icon-relatedlink.png

700 ms

icon-twitterbird.png

icon-twitterbird.png

697 ms

icon-facebook.png

icon-facebook.png

700 ms

3XaI8mzWBSs.js

3XaI8mzWBSs.js

504 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

479 ms

__utm.gif

__utm.gif

246 ms

__utm.gif

__utm.gif

196 ms

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

tweet_button.fd774b599f565016d763dd860cb31c79.ja.html

259 ms

follow_button.fd774b599f565016d763dd860cb31c79.ja.html

follow_button.fd774b599f565016d763dd860cb31c79.ja.html

256 ms

ping

ping

147 ms

comments.php

comments.php

791 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

168 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

258 ms

fastbutton

fastbutton

681 ms

like.php

like.php

653 ms

like.php

like.php

728 ms

share_button.html

share_button.html

1055 ms

postmessageRelay

postmessageRelay

1143 ms

lift.json

lift.json

731 ms

rs=AGLTcCPnvMBJ32ao-vxx78giqcGO6TMjFw

rs=AGLTcCPnvMBJ32ao-vxx78giqcGO6TMjFw

335 ms

ZGOkkXtw5CU.css

ZGOkkXtw5CU.css

326 ms

CY9MHqPubFR.css

CY9MHqPubFR.css

837 ms

RSKXsTpcgW9.css

RSKXsTpcgW9.css

1037 ms

X3aU9gBqbk3.css

X3aU9gBqbk3.css

874 ms

SRSW8M763HA.js

SRSW8M763HA.js

1705 ms

ldIMPsSoKmy.js

ldIMPsSoKmy.js

1703 ms

y97Ig99UVTs.js

y97Ig99UVTs.js

1076 ms

rR4Qw0p7TFQ.js

rR4Qw0p7TFQ.js

1941 ms

ULtnh-HfQSw.js

ULtnh-HfQSw.js

1694 ms

Cw6QosZRsiU.js

Cw6QosZRsiU.js

1689 ms

FOagnU9QnXq.js

FOagnU9QnXq.js

1067 ms

O3W7iparFI2.js

O3W7iparFI2.js

1674 ms

dt0QadAXRnm.js

dt0QadAXRnm.js

2393 ms

KanoMJZ9xtG.js

KanoMJZ9xtG.js

2388 ms

ye4Amg-qrtc.js

ye4Amg-qrtc.js

2389 ms

d_-F4IIjJo3.js

d_-F4IIjJo3.js

2391 ms

3poIqqWXpbT.js

3poIqqWXpbT.js

2823 ms

KHAtULXOQuz.js

KHAtULXOQuz.js

2986 ms

3XaI8mzWBSs.js

3XaI8mzWBSs.js

5288 ms

1662 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

628 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

628 ms

grlryt2bdKIyfMSOhzd1eA.woff

grlryt2bdKIyfMSOhzd1eA.woff

4793 ms

sync.html

sync.html

1226 ms

share_button.php

share_button.php

1279 ms

original.jpg

original.jpg

8193 ms

bc

bc

1257 ms

original.jpg

original.jpg

8267 ms

bc

bc

1253 ms

bt_check_1_r001.png

bt_check_1_r001.png

4376 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

4216 ms

rpc:shindig_random.js

rpc:shindig_random.js

57 ms

sync.js

sync.js

3520 ms

3XaI8mzWBSs.js

3XaI8mzWBSs.js

3462 ms

reset.css

reset.css

3327 ms

entry-button.css

entry-button.css

3323 ms

12661952_1133505229995113_3703099190983113039_n.jpg

12661952_1133505229995113_3703099190983113039_n.jpg

677 ms

like.png

like.png

397 ms

fav.png

fav.png

148 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

132 ms

gm-8CYVMZ_l.png

gm-8CYVMZ_l.png

132 ms

bbtn-l_v3.png

bbtn-l_v3.png

109 ms

push_sync

push_sync

2684 ms

set

set

894 ms

cookiesync

cookiesync

2175 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

110 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

55 ms

i8XO-4kv8i7.js

i8XO-4kv8i7.js

54 ms

jot.html

jot.html

144 ms

Accessibility Review

ozeki.fa-fa.com accessibility score

53

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ozeki.fa-fa.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ozeki.fa-fa.com SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozeki.fa-fa.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Ozeki.fa-fa.com main page’s claimed encoding is euc-jp. 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

ozeki.fa-fa.com

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