Tools & Wizards About Us
emergency.co.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

emergency.co.jp

日本エマージェンシーアシスタンス株式会社（EAJ） | 海外での危機管理や緊急医療対応を支援

Page Load Speed

6.3 sec in total

First Response

494 ms

Resources Loaded

5.5 sec

Page Rendered

281 ms

emergency.co.jp screenshot

About Website

Click here to check amazing Emergency content for Japan. Otherwise, check out these important facts you probably never knew about emergency.co.jp

日本エマージェンシーアシスタンスは、海外での危機管理・緊急医療対応や、セキュリティ対策、リスクマネージメント、日本への医療目的渡航をサポートする会社です。

Visit emergency.co.jp

Key Findings

We analyzed Emergency.co.jp page load time and found that the first response time was 494 ms and then it took 5.8 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

emergency.co.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value10.4 s

8/100

10%

TBT (Total Blocking Time)

Value1,670 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

emergency.co.jp

494 ms

emergency.co.jp

1017 ms

jquery.js

874 ms

jquery.common.js

1051 ms

root.css

528 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 76% of them (44 requests) were addressed to the original Emergency.co.jp, 14% (8 requests) were made to Ssl4.eir-parts.net and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Emergency.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 380.3 kB (14%)

Content Size

2.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 16.6 kB

  • Original 23.0 kB
  • After minification 20.9 kB
  • After compression 6.4 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 16.6 kB or 72% of the original size.

Image Optimization

-5%

Potential reduce by 111.1 kB

  • Original 2.3 MB
  • After minification 2.1 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. Emergency images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 196.9 kB

  • Original 357.0 kB
  • After minification 346.3 kB
  • After compression 160.1 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 196.9 kB or 55% of the original size.

CSS Optimization

-80%

Potential reduce by 55.7 kB

  • Original 69.6 kB
  • After minification 60.8 kB
  • After compression 13.9 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. Emergency.co.jp needs all CSS files to be minified and compressed as it can save up to 55.7 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (42%)

Requests Now

55

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

emergency.co.jp

emergency.co.jp

494 ms

emergency.co.jp

emergency.co.jp

1017 ms

jquery.js

jquery.js

874 ms

jquery.common.js

jquery.common.js

1051 ms

root.css

root.css

528 ms

font-awesome.min.css

font-awesome.min.css

42 ms

index.css

index.css

527 ms

jquery.bgswitcher.js

jquery.bgswitcher.js

530 ms

jquery.bxslider.css

jquery.bxslider.css

567 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

883 ms

cookieconsent.min.css

cookieconsent.min.css

26 ms

cookieconsent.min.js

cookieconsent.min.js

33 ms

eir_v5.js

eir_v5.js

531 ms

reset.css

reset.css

176 ms

base.css

base.css

351 ms

content.css

content.css

190 ms

gtm.js

gtm.js

169 ms

analytics.js

analytics.js

140 ms

logo_header01.gif

logo_header01.gif

180 ms

btn_header_contact.gif

btn_header_contact.gif

180 ms

btn_header_contact_ov.gif

btn_header_contact_ov.gif

193 ms

mv_img01.jpg

mv_img01.jpg

1966 ms

mv_txt_bg.png

mv_txt_bg.png

180 ms

mv_copy.png

mv_copy.png

352 ms

mv_copy03.png

mv_copy03.png

353 ms

service_thumb01.jpg

service_thumb01.jpg

535 ms

service_thumb02.jpg

service_thumb02.jpg

881 ms

service_thumb03.jpg

service_thumb03.jpg

1334 ms

service_thumb04.jpg

service_thumb04.jpg

881 ms

service_thumb05.jpg

service_thumb05.jpg

708 ms

service_thumb06.jpg

service_thumb06.jpg

880 ms

top_banner06.png

top_banner06.png

881 ms

top_banner08.jpg

top_banner08.jpg

1063 ms

top_banner01.png

top_banner01.png

1598 ms

top_banner07.png

top_banner07.png

1063 ms

top_banner02.png

top_banner02.png

1064 ms

top_banner03.png

top_banner03.png

1244 ms

top_banner04.jpg

top_banner04.jpg

1244 ms

top_banner05.jpg

top_banner05.jpg

1244 ms

top_banner09.png

top_banner09.png

1597 ms

logo_footer_privacy01.gif

logo_footer_privacy01.gif

1407 ms

logo_footer_jpx01.gif

logo_footer_jpx01.gif

1408 ms

logo_footer_mej01.gif

logo_footer_mej01.gif

1524 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

58 ms

eir_common.js

eir_common.js

1122 ms

btn_conversion.gif

btn_conversion.gif

1485 ms

btn_pagetop.png

btn_pagetop.png

1485 ms

btn_pagetop_ov.png

btn_pagetop_ov.png

1582 ms

mv_img02.jpg

mv_img02.jpg

2335 ms

mv_img03.jpg

mv_img03.jpg

2337 ms

main.css

main.css

178 ms

util.js

util.js

513 ms

common_conf.js

common_conf.js

187 ms

eir_main.js

eir_main.js

196 ms

custom.js

custom.js

203 ms

file_top_001.js

file_top_001.js

168 ms

print.css

print.css

177 ms

drawHtml.js

drawHtml.js

191 ms

Accessibility Review

emergency.co.jp accessibility score

89

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

Image elements do not have [alt] attributes

Best Practices

emergency.co.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

emergency.co.jp SEO score

58

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

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 Emergency.co.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 Emergency.co.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

emergency.co.jp

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