Tools & Wizards About Us
fxr.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

fxr.jp

表参道のお部屋探し | こだわり賃貸 エフバイアール不動産

Page Load Speed

16.3 sec in total

First Response

6.7 sec

Resources Loaded

9.2 sec

Page Rendered

298 ms

fxr.jp screenshot

About Website

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

表参道、原宿、青山のこだわり賃貸ならエフバイアール不動産へ。神宮前、外苑前、北青山、南青山エリアを中心とした渋谷区、港区の賃貸物件検索、比較サイト。来店不要、メールやLINE、facebookでお部屋探しができます。初期費用クレジット決済可能。

Visit fxr.jp

Key Findings

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

Performance Metrics

fxr.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

fxr.jp

6727 ms

css

25 ms

style2012.css

646 ms

corners2012.css

661 ms

dashicons.min.css

893 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Fxr.jp, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Fxr.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.1 kB (62%)

Content Size

823.0 kB

After Optimization

312.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fxr.jp main page is 823.0 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. CSS take 306.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 61.0 kB

  • Original 74.7 kB
  • After minification 67.3 kB
  • After compression 13.8 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 61.0 kB or 82% of the original size.

Image Optimization

-30%

Potential reduce by 64.0 kB

  • Original 214.9 kB
  • After minification 150.9 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, Fxr needs image optimization as it can save up to 64.0 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 150.2 kB

  • Original 227.1 kB
  • After minification 194.9 kB
  • After compression 77.0 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 150.2 kB or 66% of the original size.

CSS Optimization

-77%

Potential reduce by 235.0 kB

  • Original 306.3 kB
  • After minification 240.6 kB
  • After compression 71.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. Fxr.jp needs all CSS files to be minified and compressed as it can save up to 235.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (53%)

Requests Now

59

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fxr.jp

fxr.jp

6727 ms

css

css

25 ms

style2012.css

style2012.css

646 ms

corners2012.css

corners2012.css

661 ms

dashicons.min.css

dashicons.min.css

893 ms

thickbox.css

thickbox.css

542 ms

styles.css

styles.css

327 ms

genericons.css

genericons.css

809 ms

style.css

style.css

1301 ms

wpp.css

wpp.css

615 ms

lightbox.min.css

lightbox.min.css

668 ms

jquery.js

jquery.js

1177 ms

jquery-migrate.min.js

jquery-migrate.min.js

782 ms

css

css

13 ms

fontello.css

fontello.css

833 ms

jquery.bxslider.css

jquery.bxslider.css

931 ms

jquery.min.js

jquery.min.js

6 ms

jquery.bxslider.js

jquery.bxslider.js

1095 ms

jquery.rwdImageMaps.js

jquery.rwdImageMaps.js

969 ms

blog.css

blog.css

996 ms

jquery.js%22

jquery.js%22

966 ms

oritatami.js

oritatami.js

829 ms

jquery.flatheights.js

jquery.flatheights.js

711 ms

platform.js

platform.js

50 ms

thickbox.js

thickbox.js

805 ms

jquery.form.min.js

jquery.form.min.js

885 ms

scripts.js

scripts.js

835 ms

jquery.masonry.min.js

jquery.masonry.min.js

885 ms

functions.js

functions.js

909 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

963 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

994 ms

404.html

404.html

370 ms

sdk.js

sdk.js

17 ms

style.css

style.css

797 ms

37 ms

ga.js

ga.js

66 ms

logo.png

logo.png

204 ms

logo-title_n.png

logo-title_n.png

207 ms

head-tel.png

head-tel.png

206 ms

intro-main.png

intro-main.png

366 ms

%E3%83%97%E3%83%AB%E3%83%A1%E3%83%AA%E3%82%A2%E4%B8%89%E8%BB%92%E8%8C%B6%E5%B1%8B101_03-150x150.jpg

%E3%83%97%E3%83%AB%E3%83%A1%E3%83%AA%E3%82%A2%E4%B8%89%E8%BB%92%E8%8C%B6%E5%B1%8B101_03-150x150.jpg

207 ms

%E3%83%9E%E3%83%AA%E3%82%AA%E3%83%B3%E5%8D%97%E9%9D%92%E5%B1%B11301_01-150x150.jpg

%E3%83%9E%E3%83%AA%E3%82%AA%E3%83%B3%E5%8D%97%E9%9D%92%E5%B1%B11301_01-150x150.jpg

204 ms

fxr3327-8-150x150.jpg

fxr3327-8-150x150.jpg

319 ms

fxr5218-4-150x150.jpg

fxr5218-4-150x150.jpg

326 ms

duesannguu06-150x150.jpg

duesannguu06-150x150.jpg

489 ms

yoyogi01-150x150.jpg

yoyogi01-150x150.jpg

338 ms

duehatagaya003-150x150.jpg

duehatagaya003-150x150.jpg

370 ms

K-house_01-150x150.jpg

K-house_01-150x150.jpg

477 ms

fenikusu005-150x150.jpg

fenikusu005-150x150.jpg

483 ms

shibuyakan005-150x150.jpg

shibuyakan005-150x150.jpg

507 ms

syoutoufive001-150x150.jpg

syoutoufive001-150x150.jpg

549 ms

%E3%82%A8%E3%82%AF%E3%82%BB%E3%83%AC%E3%83%B3%E3%83%88%E3%83%AF%E3%83%B3503_02-150x150.jpg

%E3%82%A8%E3%82%AF%E3%82%BB%E3%83%AC%E3%83%B3%E3%83%88%E3%83%AF%E3%83%B3503_02-150x150.jpg

548 ms

%E3%82%A8%E3%82%B0%E3%82%BC%E3%82%AF%E3%83%86%E3%82%A3%E3%83%96%E5%8E%9F%E5%AE%BF304_03-150x150.jpg

%E3%82%A8%E3%82%B0%E3%82%BC%E3%82%AF%E3%83%86%E3%82%A3%E3%83%96%E5%8E%9F%E5%AE%BF304_03-150x150.jpg

636 ms

YMO%E9%A7%92%E6%BE%A4302_01-150x150.jpg

YMO%E9%A7%92%E6%BE%A4302_01-150x150.jpg

643 ms

FeelA%E6%B8%8B%E8%B0%B7913_03-150x150.jpg

FeelA%E6%B8%8B%E8%B0%B7913_03-150x150.jpg

652 ms

K-house_02-150x150.jpg

K-house_02-150x150.jpg

675 ms

fontello.woff

fontello.woff

677 ms

FWNn6ITYqL6or7ZTmBxRhu921tOcMok2fHawGmtxikA.ttf

FWNn6ITYqL6or7ZTmBxRhu921tOcMok2fHawGmtxikA.ttf

22 ms

__utm.gif

__utm.gif

64 ms

widgets.js

widgets.js

85 ms

xd_arbiter.php

xd_arbiter.php

23 ms

xd_arbiter.php

xd_arbiter.php

40 ms

loadingAnimation.gif

loadingAnimation.gif

529 ms

Accessibility Review

fxr.jp accessibility score

86

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

fxr.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fxr.jp SEO score

100

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

fxr.jp

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