Tools & Wizards About Us
forestbell.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

forestbell.jp

名古屋市守山区の産婦人科 フォレストベルクリニック

Page Load Speed

7.4 sec in total

First Response

643 ms

Resources Loaded

6 sec

Page Rendered

750 ms

forestbell.jp screenshot

About Website

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

名古屋市守山区の産婦人科・小児科・漢方婦人科。無痛分娩、立会い分娩にも対応しています。ネットご予約受付中です。【春日井市・瀬戸市・尾張旭市】

Visit forestbell.jp

Key Findings

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

Performance Metrics

forestbell.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

forestbell.jp

643 ms

forestbell.jp

710 ms

www.forestbell.jp

976 ms

gtm.js

65 ms

style.css

198 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 82% of them (63 requests) were addressed to the original Forestbell.jp, 5% (4 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Forestbell.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 103.2 kB (3%)

Content Size

3.0 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 50.9 kB

  • Original 62.8 kB
  • After minification 52.6 kB
  • After compression 12.0 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 10.3 kB, which is 16% 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 50.9 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 19.9 kB

  • Original 2.8 MB
  • After minification 2.8 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. Forestbell images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 10.7 kB

  • Original 123.3 kB
  • After minification 123.3 kB
  • After compression 112.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. This website has mostly compressed JavaScripts.

CSS Optimization

-36%

Potential reduce by 21.6 kB

  • Original 60.2 kB
  • After minification 59.4 kB
  • After compression 38.6 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. Forestbell.jp needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (51%)

Requests Now

68

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forestbell. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

forestbell.jp

forestbell.jp

643 ms

forestbell.jp

forestbell.jp

710 ms

www.forestbell.jp

www.forestbell.jp

976 ms

gtm.js

gtm.js

65 ms

style.css

style.css

198 ms

content.css

content.css

395 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

513 ms

pages.css

pages.css

765 ms

home.css

home.css

577 ms

all.css

all.css

38 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

26 ms

velocity.min.js

velocity.min.js

588 ms

default.js

default.js

588 ms

content.js

content.js

589 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

682 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

773 ms

pages.js

pages.js

785 ms

modernizr-custom.js

modernizr-custom.js

786 ms

lazysizes.js

lazysizes.js

785 ms

home.js

home.js

851 ms

js

js

56 ms

import.css

import.css

761 ms

base.css

base.css

197 ms

common.css

common.css

198 ms

clear.css

clear.css

192 ms

sdk.js

sdk.js

162 ms

embed

embed

342 ms

logoHeader.png

logoHeader.png

306 ms

logoHeaderText.svg

logoHeaderText.svg

307 ms

gNavIco_svg1.svg

gNavIco_svg1.svg

301 ms

gNavIco_svg2.svg

gNavIco_svg2.svg

304 ms

gNavIco_svg3.svg

gNavIco_svg3.svg

278 ms

gNavIco_svg4.svg

gNavIco_svg4.svg

299 ms

gNavIco_svg5.svg

gNavIco_svg5.svg

448 ms

btnMenuOpen.png

btnMenuOpen.png

491 ms

gNavIco01.png

gNavIco01.png

491 ms

gNavIco02.png

gNavIco02.png

501 ms

gNavIco04.png

gNavIco04.png

502 ms

gNavIco08.png

gNavIco08.png

501 ms

gNavIco06.png

gNavIco06.png

618 ms

01_forestbell_web_TOP_02.jpg

01_forestbell_web_TOP_02.jpg

1638 ms

01_forestbell_web_TOP_03.jpg

01_forestbell_web_TOP_03.jpg

1823 ms

01_forestbell_web_TOP_04.jpg

01_forestbell_web_TOP_04.jpg

1873 ms

btnScroll.png

btnScroll.png

697 ms

bgImage02.jpg

bgImage02.jpg

1091 ms

arr02.png

arr02.png

788 ms

bgSlash01.png

bgSlash01.png

894 ms

bgImage01.jpg

bgImage01.jpg

1127 ms

bgImage03.jpg

bgImage03.jpg

1286 ms

bgImage04.jpg

bgImage04.jpg

1288 ms

bgImage20.jpg

bgImage20.jpg

1635 ms

arr05.png

arr05.png

1483 ms

bgImage21.jpg

bgImage21.jpg

1880 ms

bgImage10.jpg

bgImage10.jpg

1681 ms

bgImage11.jpg

bgImage11.jpg

1975 ms

bgImage16.jpg

bgImage16.jpg

1829 ms

bgImage17.jpg

bgImage17.jpg

2075 ms

arr01.png

arr01.png

2013 ms

icoBlank.png

icoBlank.png

2020 ms

bnr23.webp

bnr23.webp

2069 ms

icoPopup.png

icoPopup.png

2078 ms

bnr10.gif

bnr10.gif

2145 ms

logoFooter.png

logoFooter.png

2105 ms

fa-brands-400.woff

fa-brands-400.woff

58 ms

result.jsonp

result.jsonp

971 ms

sdk.js

sdk.js

22 ms

31 ms

NotoSansCJKjp-Medium.woff

NotoSansCJKjp-Medium.woff

2129 ms

NotoSansCJKjp-Regular.woff

NotoSansCJKjp-Regular.woff

1999 ms

Roboto-Regular.woff

Roboto-Regular.woff

1983 ms

Roboto-Medium.woff

Roboto-Medium.woff

1995 ms

logoFooterText.svg

logoFooterText.svg

2019 ms

logoKishokai.png

logoKishokai.png

2092 ms

js

js

31 ms

search.js

search.js

3 ms

geometry.js

geometry.js

6 ms

main.js

main.js

10 ms

Accessibility Review

forestbell.jp accessibility score

90

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

Best Practices

forestbell.jp 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

forestbell.jp SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

forestbell.jp

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