Tools & Wizards About Us
looop.co.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

looop.co.jp

株式会社 L o o o p (ループ) 企業サイト | 再生可能エネルギーの最大普及を目指す電力会社

Page Load Speed

5.9 sec in total

First Response

472 ms

Resources Loaded

4.9 sec

Page Rendered

465 ms

looop.co.jp screenshot

About Website

Welcome to looop.co.jp homepage info - get ready to check L O P best content for Japan right away, or after learning these important things about looop.co.jp

再生可能エネルギーの最大普及を通じた「エネルギーフリー社会」の実現を目指す電力会社、株式会社Looop(ループ)の企業サイトです。会社情報や事業紹介、太陽光発電を中心としたサービスやテクノロジーなど様々な取り組みなどを掲載しています。

Visit looop.co.jp

Key Findings

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

looop.co.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

looop.co.jp

472 ms

looop.co.jp

974 ms

top.css

469 ms

jquery-1.11.1.min.js

1034 ms

jquery.plugins.js

740 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 69% of them (72 requests) were addressed to the original Looop.co.jp, 5% (5 requests) were made to Google.com and 4% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Looop.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 787.0 kB (41%)

Content Size

1.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Looop.co.jp main page is 1.9 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. 55% of websites need less resources to load. Images take 936.5 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 42.8 kB

  • Original 62.3 kB
  • After minification 59.9 kB
  • After compression 19.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 42.8 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 77.6 kB

  • Original 936.5 kB
  • After minification 858.9 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. L O P images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 330.5 kB

  • Original 508.1 kB
  • After minification 487.7 kB
  • After compression 177.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 330.5 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 336.1 kB

  • Original 398.9 kB
  • After minification 363.0 kB
  • After compression 62.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. Looop.co.jp needs all CSS files to be minified and compressed as it can save up to 336.1 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

96

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

looop.co.jp

looop.co.jp

472 ms

looop.co.jp

looop.co.jp

974 ms

top.css

top.css

469 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1034 ms

jquery.plugins.js

jquery.plugins.js

740 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

745 ms

slick.min.js

slick.min.js

801 ms

common.js

common.js

643 ms

top.js

top.js

626 ms

jQueryAutoHeight_top.js

jQueryAutoHeight_top.js

785 ms

smp_top.js

smp_top.js

802 ms

s_retargeting.js

s_retargeting.js

1001 ms

conversion.js

conversion.js

49 ms

mrhs8jc69f.js

mrhs8jc69f.js

50 ms

iframe_api

iframe_api

101 ms

lb

lb

72 ms

bg_img.jpg

bg_img.jpg

1627 ms

cover.gif

cover.gif

173 ms

bg_opacity_50.png

bg_opacity_50.png

174 ms

nav-global_01.png

nav-global_01.png

176 ms

nav-global_02.png

nav-global_02.png

176 ms

nav-global_03.png

nav-global_03.png

172 ms

nav-global_08.png

nav-global_08.png

322 ms

nav-global_05.png

nav-global_05.png

324 ms

nav-global_06.png

nav-global_06.png

322 ms

btn_header_01.png

btn_header_01.png

347 ms

txt_tel_01.png

txt_tel_01.png

348 ms

hdg_top_copy.png

hdg_top_copy.png

614 ms

bg_panel.png

bg_panel.png

479 ms

tag_new.png

tag_new.png

480 ms

pct_panel_19.png

pct_panel_19.png

650 ms

pct_panel_20.png

pct_panel_20.png

648 ms

pct_panel_23.png

pct_panel_23.png

615 ms

pct_panel_12.jpg

pct_panel_12.jpg

767 ms

pct_panel_22.png

pct_panel_22.png

912 ms

pct_panel_21.png

pct_panel_21.png

763 ms

pct_panel_14.jpg

pct_panel_14.jpg

964 ms

pct_panel_18.png

pct_panel_18.png

1123 ms

icon_arrow.png

icon_arrow.png

910 ms

icon_panel_01.png

icon_panel_01.png

916 ms

icon_panel_02.png

icon_panel_02.png

1057 ms

icon_panel_03.png

icon_panel_03.png

1058 ms

icon_panel_04.png

icon_panel_04.png

1064 ms

btn_panel_15.png

btn_panel_15.png

1122 ms

ttl_news.png

ttl_news.png

1204 ms

btn_more_02.png

btn_more_02.png

1205 ms

ttl_media.png

ttl_media.png

1212 ms

bnr_top_11.png

bnr_top_11.png

1281 ms

bnr_footer_02.png

bnr_footer_02.png

1282 ms

bnr_footer_03.png

bnr_footer_03.png

1351 ms

bnr_footer_04.png

bnr_footer_04.png

1355 ms

ga.js

ga.js

114 ms

tag.js

tag.js

56 ms

segmentation.js

segmentation.js

159 ms

btn_site_07.png

btn_site_07.png

1327 ms

www-widgetapi.js

www-widgetapi.js

110 ms

gtm.js

gtm.js

148 ms

tag

tag

93 ms

pix.js

pix.js

910 ms

img

img

1080 ms

__utm.gif

__utm.gif

32 ms

58 ms

btn_site_03.png

btn_site_03.png

1270 ms

btn_site_01.png

btn_site_01.png

1271 ms

btn_site_06.png

btn_site_06.png

1331 ms

btn_search_01.png

btn_search_01.png

1332 ms

btn_pagetop.png

btn_pagetop.png

1340 ms

46 ms

collect

collect

66 ms

cnt

cnt

691 ms

conversion_async.js

conversion_async.js

22 ms

_z1yx-dWcnc

_z1yx-dWcnc

71 ms

beacon.html

beacon.html

32 ms

16 ms

15 ms

ga-audiences

ga-audiences

21 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

23 ms

www-embed-player.js

www-embed-player.js

50 ms

base.js

base.js

97 ms

btn_sns_02.png

btn_sns_02.png

1279 ms

nav-global_01_o.png

nav-global_01_o.png

1281 ms

nav-global_02_o.png

nav-global_02_o.png

1327 ms

nav-global_03_o.png

nav-global_03_o.png

1307 ms

nav-global_08_o.png

nav-global_08_o.png

1316 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

8 ms

ad_status.js

ad_status.js

47 ms

nav-global_05_o.png

nav-global_05_o.png

1279 ms

nav-global_06_o.png

nav-global_06_o.png

1278 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

65 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

74 ms

btn_header_01_o.png

btn_header_01_o.png

1168 ms

btn_panel_15_o.png

btn_panel_15_o.png

1182 ms

bnr_top_11_o.png

bnr_top_11_o.png

1155 ms

bnr_footer_02_o.png

bnr_footer_02_o.png

1163 ms

bnr_footer_03_o.png

bnr_footer_03_o.png

1154 ms

bnr_footer_04_o.png

bnr_footer_04_o.png

1150 ms

btn_site_07_o.png

btn_site_07_o.png

1029 ms

btn_site_03_o.png

btn_site_03_o.png

1031 ms

btn_site_01_o.png

btn_site_01_o.png

1034 ms

btn_site_06_o.png

btn_site_06_o.png

996 ms

btn_sns_02_o.png

btn_sns_02_o.png

1019 ms

reset.css

reset.css

160 ms

smp_main.css

smp_main.css

160 ms

pd.js

pd.js

175 ms

Accessibility Review

looop.co.jp accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

looop.co.jp best practices score

83

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

SEO Factors

looop.co.jp SEO score

91

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

High

Tap targets are not sized appropriately

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

looop.co.jp

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