Tools & Wizards About Us
areaers.jp screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

areaers.jp

ITで地方創生 Areaers(エリアーズ)　地域活性化,地域・エリアプロモーション,地域ポータルサイト,ブログ

Page Load Speed

5.2 sec in total

First Response

797 ms

Resources Loaded

4.1 sec

Page Rendered

283 ms

areaers.jp screenshot

About Website

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

ITによる地方創生・地域活性化を目指す全国地域ブログネットワーク「Areaers（エリアーズ）」公式サイト。 単なるインターネット上の情報発信を目的とするのではなく、人と人、人と地域のお店や企業、NPO団体との繋がりを創出し、新しい時代にマッチしたリアルな地域コミュニティを創造することが、私たちのミッションです。 北海道から沖縄まで、全国40エリア以上に展開する地域密着型サイトの活動の中から、地域...

Visit areaers.jp

Key Findings

We analyzed Areaers.jp page load time and found that the first response time was 797 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

areaers.jp performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,980 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.375

28/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

areaers.jp

797 ms

style.css

762 ms

jquery.min.js

23 ms

partnerlink2019.css

936 ms

js

85 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Areaers.jp, 35% (19 requests) were made to Platform.twitter.com and 18% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Img01.osakazine.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.1 kB (3%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-72%

Potential reduce by 25.9 kB

  • Original 36.2 kB
  • After minification 35.0 kB
  • After compression 10.3 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 25.9 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 18.9 kB

  • Original 2.1 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. Areaers images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 8.9 kB

  • Original 46.2 kB
  • After minification 46.0 kB
  • After compression 37.3 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 8.9 kB or 19% of the original size.

CSS Optimization

-82%

Potential reduce by 22.4 kB

  • Original 27.2 kB
  • After minification 19.9 kB
  • After compression 4.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. Areaers.jp needs all CSS files to be minified and compressed as it can save up to 22.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (67%)

Requests Now

54

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

areaers.jp

areaers.jp

797 ms

style.css

style.css

762 ms

jquery.min.js

jquery.min.js

23 ms

partnerlink2019.css

partnerlink2019.css

936 ms

js

js

85 ms

script.php

script.php

744 ms

rss_reader.php

rss_reader.php

1111 ms

widgets.js

widgets.js

108 ms

sdk.js

sdk.js

50 ms

arealink.js

arealink.js

540 ms

widgets.js

widgets.js

59 ms

slick.css

slick.css

44 ms

slick.min.js

slick.min.js

40 ms

arrow_right.png

arrow_right.png

171 ms

head_PC_1.png

head_PC_1.png

1077 ms

icon_tw.png

icon_tw.png

536 ms

hamamachi.png

hamamachi.png

2239 ms

areaers_tamaliver200623.png

areaers_tamaliver200623.png

1740 ms

areaers_0605_kyo2.png

areaers_0605_kyo2.png

1477 ms

icon_fb.png

icon_fb.png

549 ms

sdk.js

sdk.js

19 ms

style.css

style.css

339 ms

107 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

page.php

page.php

225 ms

settings

settings

69 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

Areaersjp

Areaersjp

67 ms

BcW4HD-pxEe.css

BcW4HD-pxEe.css

127 ms

AkV4cevgxL7.js

AkV4cevgxL7.js

25 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

20 ms

HbT8HXdZYIC.js

HbT8HXdZYIC.js

25 ms

Ue-M3hwtZyC.js

Ue-M3hwtZyC.js

24 ms

TwSfsj5nvl7.js

TwSfsj5nvl7.js

23 ms

p55HfXW__mM.js

p55HfXW__mM.js

22 ms

-GcgCtiMgBN.js

-GcgCtiMgBN.js

25 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

28 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

50 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

72 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

81 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

99 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

102 ms

_buildManifest.js

_buildManifest.js

111 ms

_ssgManifest.js

_ssgManifest.js

112 ms

305108019_444478847700508_6045014364924765612_n.png

305108019_444478847700508_6045014364924765612_n.png

78 ms

m_xSm6749Zq.js

m_xSm6749Zq.js

27 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

25 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

38 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

36 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

21 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

42 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

51 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

55 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

26 ms

page.php

page.php

169 ms

Accessibility Review

areaers.jp accessibility score

53

Accessibility Issues

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

areaers.jp SEO score

90

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

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Areaers.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 Areaers.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

areaers.jp

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