Tools & Wizards About Us
efo-cube.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

efo-cube.info

EFO（入力フォーム最適化）ならEFO CUBE

Page Load Speed

4.4 sec in total

First Response

521 ms

Resources Loaded

3.5 sec

Page Rendered

310 ms

efo-cube.info screenshot

About Website

Click here to check amazing EFO CUBE content for Japan. Otherwise, check out these important facts you probably never knew about efo-cube.info

株式会社GeeeNのEFO（入力フォーム最適化）ツール「EFO CUBE」の公式サイトです。業界最高レベルの機能数、4,200フォーム以上の導入実績のあるEFOCUBEはタグ設置いただくだけで導入可能です。ツールのみではない充実のサポートでEFOを導入しませんか？

Visit efo-cube.info

Key Findings

We analyzed Efo-cube.info page load time and found that the first response time was 521 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

efo-cube.info performance score

0

Network Requests Diagram

efo-cube.info

521 ms

import.css

293 ms

style.css

293 ms

jquery.js

587 ms

jquery.cookie.js

297 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 79% of them (56 requests) were addressed to the original Efo-cube.info, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Efo-cube.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 483.4 kB (47%)

Content Size

1.0 MB

After Optimization

538.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Efo-cube.info main page is 1.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. 65% of websites need less resources to load. Javascripts take 381.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 11.2 kB

  • Original 15.6 kB
  • After minification 13.4 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 14% 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 11.2 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 15.7 kB

  • Original 356.9 kB
  • After minification 341.2 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. EFO CUBE images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 235.0 kB

  • Original 381.5 kB
  • After minification 373.9 kB
  • After compression 146.4 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 235.0 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 221.5 kB

  • Original 267.6 kB
  • After minification 259.3 kB
  • After compression 46.0 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. Efo-cube.info needs all CSS files to be minified and compressed as it can save up to 221.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (24%)

Requests Now

67

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

efo-cube.info

efo-cube.info

521 ms

import.css

import.css

293 ms

style.css

style.css

293 ms

jquery.js

jquery.js

587 ms

jquery.cookie.js

jquery.cookie.js

297 ms

common.js

common.js

298 ms

heightLine.js

heightLine.js

432 ms

jquery.min.js

jquery.min.js

89 ms

modalwindow.js

modalwindow.js

585 ms

conversion.js

conversion.js

54 ms

s_retargeting.js

s_retargeting.js

620 ms

cmn_layout.css

cmn_layout.css

294 ms

cmn_style.css

cmn_style.css

299 ms

analytics.js

analytics.js

124 ms

bg_body_1.gif

bg_body_1.gif

166 ms

logo.png

logo.png

334 ms

btn_hrd01_no.png

btn_hrd01_no.png

330 ms

bg_body_2.gif

bg_body_2.gif

328 ms

gnavi01_ac.png

gnavi01_ac.png

331 ms

gnavi02_no.png

gnavi02_no.png

331 ms

gnavi03_no.png

gnavi03_no.png

471 ms

gnavi04_no.png

gnavi04_no.png

621 ms

gnavi05_no.png

gnavi05_no.png

617 ms

gnavi06_no.png

gnavi06_no.png

619 ms

gnavi07_no.png

gnavi07_no.png

616 ms

bg_mainpic.gif

bg_mainpic.gif

618 ms

mainpic_index.jpg

mainpic_index.jpg

1338 ms

btn_sample05.png

btn_sample05.png

906 ms

pic_index01.jpg

pic_index01.jpg

1198 ms

pic_index01_btn.gif

pic_index01_btn.gif

908 ms

h3_index01.gif

h3_index01.gif

908 ms

pic_index02.jpg

pic_index02.jpg

1053 ms

txt_index01.gif

txt_index01.gif

1197 ms

icon_lnavi01.gif

icon_lnavi01.gif

1199 ms

pic_index03.jpg

pic_index03.jpg

1346 ms

txt_index02.gif

txt_index02.gif

1345 ms

h3_index02.gif

h3_index02.gif

1487 ms

bg_sample01.gif

bg_sample01.gif

1488 ms

btn_sample02_no.png

btn_sample02_no.png

1489 ms

img_lnavi01.gif

img_lnavi01.gif

1625 ms

btn_lnavi01_no.png

btn_lnavi01_no.png

1636 ms

img_lnavi02.gif

img_lnavi02.gif

1637 ms

bg_lnavi01.gif

bg_lnavi01.gif

1778 ms

img_lnavi03.gif

img_lnavi03.gif

1776 ms

bannar03.gif

bannar03.gif

1764 ms

ytm_04.jpg

ytm_04.jpg

1901 ms

btn_pagetop_no..gif

btn_pagetop_no..gif

1911 ms

bg_footer.gif

bg_footer.gif

1912 ms

icon_footer01.gif

icon_footer01.gif

2052 ms

kjWvEgLlvWA

kjWvEgLlvWA

112 ms

97 ms

collect

collect

59 ms

btn_hrd01_on.png

btn_hrd01_on.png

1858 ms

gnavi02_on.png

gnavi02_on.png

1861 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

43 ms

www-embed-player.js

www-embed-player.js

63 ms

base.js

base.js

111 ms

81 ms

gnavi03_on.png

gnavi03_on.png

1887 ms

gnavi04_on.png

gnavi04_on.png

1900 ms

gnavi05_on.png

gnavi05_on.png

1901 ms

gnavi06_on.png

gnavi06_on.png

2037 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

16 ms

ad_status.js

ad_status.js

129 ms

gnavi07_on.png

gnavi07_on.png

1908 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

125 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

126 ms

btn_sample02_on.png

btn_sample02_on.png

1899 ms

btn_lnavi01_on.png

btn_lnavi01_on.png

1890 ms

btn_pagetop_on..gif

btn_pagetop_on..gif

1904 ms

blank.gif

blank.gif

1904 ms

SEO Factors

efo-cube.info SEO score

0

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 Efo-cube.info 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 Efo-cube.info 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

efo-cube.info

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