Tools & Wizards About Us
ehime-juzen.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ehime-juzen.jp

愛媛十全医療学院附属病院｜内科｜整形外科｜リハビリ｜愛媛県

Page Load Speed

6.1 sec in total

First Response

570 ms

Resources Loaded

4.9 sec

Page Rendered

673 ms

ehime-juzen.jp screenshot

About Website

Click here to check amazing Ehime Juzen content. Otherwise, check out these important facts you probably never knew about ehime-juzen.jp

整形外科・内科・リハビリテーション科の愛媛十全医療学院附属病院の公式ホームページ。なかなかタバコ（煙草）がやめられない方のために、禁煙治療も行っています。

Visit ehime-juzen.jp

Key Findings

We analyzed Ehime-juzen.jp page load time and found that the first response time was 570 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

ehime-juzen.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value32.4 s

0/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.457

19/100

15%

TTI (Time to Interactive)

Value33.2 s

0/100

10%

Network Requests Diagram

ehime-juzen.jp

570 ms

ehime-juzen.jp

1203 ms

respond.min.js

181 ms

all.min.css

28 ms

jquery.min.js

26 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 90% of them (53 requests) were addressed to the original Ehime-juzen.jp, 2% (1 request) were made to Cdnjs.cloudflare.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ehime-juzen.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 244.3 kB (5%)

Content Size

5.2 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 28.0 kB

  • Original 34.0 kB
  • After minification 21.1 kB
  • After compression 6.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 12.9 kB, which is 38% 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 28.0 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 161.9 kB

  • Original 5.1 MB
  • After minification 4.9 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. Ehime Juzen images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 10.6 kB

  • Original 50.2 kB
  • After minification 44.2 kB
  • After compression 39.7 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 10.6 kB or 21% of the original size.

CSS Optimization

-86%

Potential reduce by 43.8 kB

  • Original 50.9 kB
  • After minification 32.5 kB
  • After compression 7.1 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. Ehime-juzen.jp needs all CSS files to be minified and compressed as it can save up to 43.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (36%)

Requests Now

55

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ehime-juzen.jp

ehime-juzen.jp

570 ms

ehime-juzen.jp

ehime-juzen.jp

1203 ms

respond.min.js

respond.min.js

181 ms

all.min.css

all.min.css

28 ms

jquery.min.js

jquery.min.js

26 ms

jquery.cookie.js

jquery.cookie.js

358 ms

infiniteslide.js

infiniteslide.js

491 ms

jquery.pause.min.js

jquery.pause.min.js

494 ms

to-top.js

to-top.js

493 ms

index.css

index.css

353 ms

xfj2ufz.js

xfj2ufz.js

225 ms

embed

embed

268 ms

logo.png

logo.png

181 ms

icon_text.svg

icon_text.svg

166 ms

icon_search.svg

icon_search.svg

244 ms

icon_qa.svg

icon_qa.svg

168 ms

icon_mail.svg

icon_mail.svg

169 ms

icon_point.svg

icon_point.svg

330 ms

menu_line.svg

menu_line.svg

335 ms

menu01.svg

menu01.svg

334 ms

menu02.svg

menu02.svg

360 ms

menu03.svg

menu03.svg

402 ms

menu04.svg

menu04.svg

494 ms

menu05.svg

menu05.svg

495 ms

menu06.svg

menu06.svg

499 ms

menu07.svg

menu07.svg

503 ms

main01.png

main01.png

1606 ms

sp_img_main.jpg

sp_img_main.jpg

1896 ms

bn_sinryo.png

bn_sinryo.png

660 ms

main_c.png

main_c.png

658 ms

icon_sinryo.svg

icon_sinryo.svg

664 ms

bg_blue.png

bg_blue.png

830 ms

icon_seikei.png

icon_seikei.png

822 ms

icon_naika.png

icon_naika.png

823 ms

img_tuin.png

img_tuin.png

1319 ms

img_nyuin.png

img_nyuin.png

1471 ms

bn_qa.png

bn_qa.png

1479 ms

bn_qi.png

bn_qi.png

1159 ms

icon_tokucho.svg

icon_tokucho.svg

1324 ms

img_sekitui.png

img_sekitui.png

1648 ms

arrow_tokucho.svg

arrow_tokucho.svg

1490 ms

img_hiza.png

img_hiza.png

1798 ms

img_kata.png

img_kata.png

1808 ms

bn_syujyutu.png

bn_syujyutu.png

1819 ms

bn_riha.png

bn_riha.png

1783 ms

bg_green.png

bg_green.png

1978 ms

img_rec.png

img_rec.png

1967 ms

1339 ms

sp_img_rec.jpg

sp_img_rec.jpg

2032 ms

arrow_rec.svg

arrow_rec.svg

1811 ms

oshigoto.jpg

oshigoto.jpg

1986 ms

icon_ac.svg

icon_ac.svg

1919 ms

bn_under3.png

bn_under3.png

1973 ms

p.gif

p.gif

38 ms

bn_under2.png

bn_under2.png

1897 ms

js

js

90 ms

bn_under1.png

bn_under1.png

1818 ms

page_top.png

page_top.png

1944 ms

index_sp.css

index_sp.css

182 ms

Accessibility Review

ehime-juzen.jp accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

ehime-juzen.jp 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

ehime-juzen.jp SEO score

83

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Ehime-juzen.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 Ehime-juzen.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

ehime-juzen.jp

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