Tools & Wizards About Us
imca.jp screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

imca.jp

远程医疗 Online Clinic by IMCA « 远程医疗 Online Clinic for Everyone

Page Load Speed

8.4 sec in total

First Response

1.9 sec

Resources Loaded

6.1 sec

Page Rendered

362 ms

imca.jp screenshot

About Website

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

who we are Geneikai Medical Group We are offering telemedicine since 2018. Our system was built own, not using ASP. Signup now what do we offer Your…

Visit imca.jp

Key Findings

We analyzed Imca.jp page load time and found that the first response time was 1.9 sec and then it took 6.4 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

imca.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

imca.jp

1947 ms

wp-emoji-release.min.js

190 ms

main_css.css

386 ms

theme.css

757 ms

jquery.fancybox.min.css

683 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 75% of them (41 requests) were addressed to the original Imca.jp, 9% (5 requests) were made to Fonts.gstatic.com and 7% (4 requests) were made to Colibriwp-work.colibriwp.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Imca.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.5 kB (10%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imca.jp main page is 1.5 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 130.6 kB

  • Original 151.0 kB
  • After minification 140.0 kB
  • After compression 20.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 130.6 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 10.2 kB

  • Original 1.1 MB
  • After minification 1.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. IMCA images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 4.3 kB

  • Original 185.1 kB
  • After minification 185.1 kB
  • After compression 180.8 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

-7%

Potential reduce by 8.4 kB

  • Original 126.2 kB
  • After minification 126.2 kB
  • After compression 117.8 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. Imca.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

46

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imca.jp

imca.jp

1947 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

190 ms

main_css.css

main_css.css

386 ms

theme.css

theme.css

757 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

683 ms

vkExUnit_style.css

vkExUnit_style.css

696 ms

style.min.css

style.min.css

709 ms

css

css

40 ms

styles.css

styles.css

703 ms

style.css

style.css

720 ms

toolbar.css

toolbar.css

866 ms

addfont.css

addfont.css

884 ms

styles.css

styles.css

893 ms

style.css

style.css

902 ms

vk-components.css

vk-components.css

924 ms

bootstrap_vk_using.css

bootstrap_vk_using.css

937 ms

block-build.css

block-build.css

1052 ms

all.min.css

all.min.css

1245 ms

jquery.min.js

jquery.min.js

1257 ms

jquery-migrate.min.js

jquery-migrate.min.js

1100 ms

searchbytag.js

searchbytag.js

1120 ms

imagesloaded.min.js

imagesloaded.min.js

1124 ms

masonry.min.js

masonry.min.js

1233 ms

colibri.js

colibri.js

1291 ms

typed.js

typed.js

1313 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1314 ms

theme.js

theme.js

1604 ms

counter.css

counter.css

1429 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1448 ms

wp-polyfill.min.js

wp-polyfill.min.js

1483 ms

index.js

index.js

1505 ms

scripts.js

scripts.js

1501 ms

element.js

element.js

48 ms

clipboard.min.js

clipboard.min.js

1679 ms

copy-button.js

copy-button.js

1680 ms

smooth-scroll.min.js

smooth-scroll.min.js

1679 ms

all.min.js

all.min.js

1717 ms

mbpair.jpg

mbpair.jpg

185 ms

bizz-1.jpg

bizz-1.jpg

727 ms

bizz-2.jpg

bizz-2.jpg

325 ms

imca-low-resolution-logo-white-on-transparent-background.png

imca-low-resolution-logo-white-on-transparent-background.png

324 ms

colibri-image-28.png

colibri-image-28.png

1089 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVcUwaEQXjM.ttf

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVcUwaEQXjM.ttf

127 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVcUwaEQXjM.ttf

169 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVcUwaEQXjM.ttf

307 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVcUwaEQXjM.ttf

306 ms

c2a-black-2.jpg

c2a-black-2.jpg

237 ms

widgets.js

widgets.js

271 ms

vk_sns.woff

vk_sns.woff

288 ms

fa-solid-900.ttf

fa-solid-900.ttf

622 ms

fa-regular-400.ttf

fa-regular-400.ttf

454 ms

flags.png

flags.png

421 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

60 ms

settings

settings

74 ms

Accessibility Review

imca.jp accessibility score

91

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

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imca.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Imca.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

imca.jp

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