Tools & Wizards About Us
jonliving.jp screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

jonliving.jp

キャッシング 申込 窓ロ

Page Load Speed

3.4 sec in total

First Response

656 ms

Resources Loaded

2.6 sec

Page Rendered

162 ms

jonliving.jp screenshot

About Website

Click here to check amazing Jonliving content. Otherwise, check out these important facts you probably never knew about jonliving.jp

アイフルプロミスSMBCモビットネットだけで申込を済ませるには、業者により指定された銀行口座を持っているなどの条件があります。しかし、身内に知ら...

Visit jonliving.jp

Key Findings

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

Performance Metrics

jonliving.jp performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

jonliving.jp

656 ms

reset.css

317 ms

base.css

347 ms

jquery.min.js

33 ms

analytics.js

49 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 47% of them (31 requests) were addressed to the original Jonliving.jp, 29% (19 requests) were made to Static.xx.fbcdn.net and 18% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Jonliving.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.6 kB (8%)

Content Size

791.1 kB

After Optimization

727.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-66%

Potential reduce by 6.8 kB

  • Original 10.3 kB
  • After minification 10.0 kB
  • After compression 3.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 6.8 kB or 66% of the original size.

Image Optimization

-2%

Potential reduce by 17.5 kB

  • Original 717.9 kB
  • After minification 700.4 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. Jonliving images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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 32.0 kB or 60% of the original size.

CSS Optimization

-73%

Potential reduce by 7.4 kB

  • Original 10.0 kB
  • After minification 7.5 kB
  • After compression 2.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. Jonliving.jp needs all CSS files to be minified and compressed as it can save up to 7.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (27%)

Requests Now

64

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jonliving.jp

jonliving.jp

656 ms

reset.css

reset.css

317 ms

base.css

base.css

347 ms

jquery.min.js

jquery.min.js

33 ms

analytics.js

analytics.js

49 ms

body-bgimg.png

body-bgimg.png

160 ms

jonliving-off.gif

jonliving-off.gif

197 ms

news-off.gif

news-off.gif

188 ms

concept-off.gif

concept-off.gif

332 ms

product-off.gif

product-off.gif

330 ms

company-off.gif

company-off.gif

334 ms

contact-off.gif

contact-off.gif

343 ms

top0.jpg

top0.jpg

1067 ms

top1.jpg

top1.jpg

1098 ms

top2.jpg

top2.jpg

1335 ms

top3.jpg

top3.jpg

1036 ms

top4.jpg

top4.jpg

1526 ms

maru.jpg

maru.jpg

823 ms

syokuninn.jpg

syokuninn.jpg

1251 ms

koujyou.jpg

koujyou.jpg

1361 ms

product.jpg

product.jpg

1236 ms

map.jpg

map.jpg

1285 ms

blog.jpg

blog.jpg

1413 ms

tonericoline.jpg

tonericoline.jpg

1426 ms

foresta.jpg

foresta.jpg

1473 ms

bettyuu.jpg

bettyuu.jpg

1507 ms

fstar.jpg

fstar.jpg

1523 ms

f.home-off.gif

f.home-off.gif

1587 ms

f.news-off.gif

f.news-off.gif

1593 ms

f.concept-off.gif

f.concept-off.gif

1653 ms

f.product-off.gif

f.product-off.gif

1669 ms

f.company-off.gif

f.company-off.gif

1677 ms

f.contact-off.gif

f.contact-off.gif

1676 ms

likebox.php

likebox.php

185 ms

collect

collect

27 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

176 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

221 ms

6qHpHChjY_J.css

6qHpHChjY_J.css

263 ms

ztINr5qMqM_.css

ztINr5qMqM_.css

334 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

351 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

376 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

298 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

296 ms

njO1TPvGzoR.js

njO1TPvGzoR.js

301 ms

1QuX41zDRrx.js

1QuX41zDRrx.js

373 ms

Oagsvfb4VWi.js

Oagsvfb4VWi.js

399 ms

LTv6ZK-5zxz.js

LTv6ZK-5zxz.js

462 ms

1FCa-btixu2.js

1FCa-btixu2.js

412 ms

10376917_639018612853319_6390089670951683382_n.jpg

10376917_639018612853319_6390089670951683382_n.jpg

221 ms

10177341_639016259520221_639929939284443514_n.jpg

10177341_639016259520221_639929939284443514_n.jpg

310 ms

12803302_959173340837843_2495330329922747636_n.jpg

12803302_959173340837843_2495330329922747636_n.jpg

399 ms

10660103_959173347504509_1763441872945082808_n.jpg

10660103_959173347504509_1763441872945082808_n.jpg

329 ms

12744698_959180037503840_3153061093152279445_n.jpg

12744698_959180037503840_3153061093152279445_n.jpg

381 ms

10660114_955091191246058_6278726900734433269_n.jpg

10660114_955091191246058_6278726900734433269_n.jpg

370 ms

12705652_955091197912724_2497960275979515695_n.jpg

12705652_955091197912724_2497960275979515695_n.jpg

350 ms

12715615_955091217912722_2701298723735959975_n.jpg

12715615_955091217912722_2701298723735959975_n.jpg

368 ms

12645101_945648692190308_1668786224803019837_n.jpg

12645101_945648692190308_1668786224803019837_n.jpg

416 ms

12651091_945648762190301_4830737510318105162_n.jpg

12651091_945648762190301_4830737510318105162_n.jpg

394 ms

11902411_868297853258726_7138470970056560351_n.jpg

11902411_868297853258726_7138470970056560351_n.jpg

419 ms

11863246_864739930281185_8534557008680833118_n.jpg

11863246_864739930281185_8534557008680833118_n.jpg

410 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

109 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

109 ms

QDwYpIaRyfG.png

QDwYpIaRyfG.png

109 ms

K00K-UgnsKu.png

K00K-UgnsKu.png

110 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

43 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

81 ms

Accessibility Review

jonliving.jp accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

jonliving.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jonliving.jp SEO score

93

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

    UTF-8

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

jonliving.jp

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