Tools & Wizards About Us
e-plan.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

e-plan.jp

あなたの夢を形に。縫製加工・板金加工・インターネットbiz e-plan（イ-プラン）

Page Load Speed

2.9 sec in total

First Response

576 ms

Resources Loaded

2.2 sec

Page Rendered

64 ms

e-plan.jp screenshot

About Website

Visit e-plan.jp now to see the best up-to-date E Plan content for Japan and also check out these interesting facts you probably never knew about e-plan.jp

e-planは、お客様の夢を形にします。縫製加工・板金加工・インターネットbizのことならe-planにご相談下さい。

Visit e-plan.jp

Key Findings

We analyzed E-plan.jp page load time and found that the first response time was 576 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

e-plan.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value0.8 s

100/100

10%

Network Requests Diagram

e-plan.jp

576 ms

css.css

182 ms

index2_menu2_01.gif

362 ms

index2_menu2_02.gif

363 ms

index2_menu2_03.gif

363 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that all of those requests were addressed to E-plan.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain E-plan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.6 kB (71%)

Content Size

13.6 kB

After Optimization

3.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of E-plan.jp main page is 13.6 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. Only 10% of websites need less resources to load. HTML takes 11.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 8.7 kB

  • Original 11.1 kB
  • After minification 10.7 kB
  • After compression 2.5 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 8.7 kB or 78% of the original size.

Image Optimization

-41%

Potential reduce by 903 B

  • Original 2.2 kB
  • After minification 1.3 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, E Plan needs image optimization as it can save up to 903 B or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-16%

Potential reduce by 36 B

  • Original 229 B
  • After minification 229 B
  • After compression 193 B

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. E-plan.jp needs all CSS files to be minified and compressed as it can save up to 36 B or 16% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

17

  • Images
  • CSS

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

Network Requests Diagram

e-plan.jp

e-plan.jp

576 ms

css.css

css.css

182 ms

index2_menu2_01.gif

index2_menu2_01.gif

362 ms

index2_menu2_02.gif

index2_menu2_02.gif

363 ms

index2_menu2_03.gif

index2_menu2_03.gif

363 ms

index2_menu2_04.gif

index2_menu2_04.gif

364 ms

index2_menu2_05.gif

index2_menu2_05.gif

364 ms

index2_menu2_06.gif

index2_menu2_06.gif

364 ms

index2_menu2_07.gif

index2_menu2_07.gif

545 ms

index2_menu2_08.gif

index2_menu2_08.gif

544 ms

index2_menu2_09.gif

index2_menu2_09.gif

543 ms

index2_menu2_10.gif

index2_menu2_10.gif

545 ms

index2_menu2_11.gif

index2_menu2_11.gif

545 ms

index2_menu2_12.gif

index2_menu2_12.gif

545 ms

spacer.gif

spacer.gif

724 ms

index2_contents_31.gif

index2_contents_31.gif

725 ms

index2_contents_32.gif

index2_contents_32.gif

724 ms

index2_contents_33.gif

index2_contents_33.gif

731 ms

index2_contents_05.gif

index2_contents_05.gif

728 ms

index2_contents_34.gif

index2_contents_34.gif

748 ms

index2_contents_07.gif

index2_contents_07.gif

904 ms

index2_contents_08.gif

index2_contents_08.gif

906 ms

index2_contents_37.gif

index2_contents_37.gif

905 ms

index2_contents_10.gif

index2_contents_10.gif

909 ms

index2_contents_11.gif

index2_contents_11.gif

911 ms

index2_contents_09.gif

index2_contents_09.gif

931 ms

index2_contents_35.gif

index2_contents_35.gif

1085 ms

index2_contents_38.gif

index2_contents_38.gif

1087 ms

index2_contents_18.gif

index2_contents_18.gif

1087 ms

index2_contents_36.gif

index2_contents_36.gif

1090 ms

index2_contents_22.gif

index2_contents_22.gif

1092 ms

index2_contents_23.gif

index2_contents_23.gif

1115 ms

index2_contents_24.gif

index2_contents_24.gif

1267 ms

index2_contents_40.gif

index2_contents_40.gif

1269 ms

ban_top.gif

ban_top.gif

1272 ms

b_kobo2.png

b_kobo2.png

1272 ms

line_160.gif

line_160.gif

1273 ms

ban_monodukuri_koubou_160_2.gif

ban_monodukuri_koubou_160_2.gif

1120 ms

ban_monodukuri_koubou_femme.gif

ban_monodukuri_koubou_femme.gif

1091 ms

ban_monodukuri_koubou_inu_160.gif

ban_monodukuri_koubou_inu_160.gif

1092 ms

groupban_carna_160.gif

groupban_carna_160.gif

1095 ms

groupban_cazz_160.gif

groupban_cazz_160.gif

1095 ms

ban_monodukuri_koubou_guych.gif

ban_monodukuri_koubou_guych.gif

1095 ms

ban_monodukuri_koubou_blog.gif

ban_monodukuri_koubou_blog.gif

1118 ms

ban_monodukuri_koubou_inu_b.gif

ban_monodukuri_koubou_inu_b.gif

1089 ms

ban_under.gif

ban_under.gif

1092 ms

infomation.gif

infomation.gif

1094 ms

line_551.gif

line_551.gif

1095 ms

page_under.gif

page_under.gif

1094 ms

Accessibility Review

e-plan.jp accessibility score

57

Accessibility Issues

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

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

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

e-plan.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

e-plan.jp SEO score

58

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

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-plan.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 E-plan.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

e-plan.jp

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