Tools & Wizards About Us
find-a.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

find-a.jp

SEOサービス　Find-A | 実績20,000社以上！SEO/SEMなら、GMOソリューションパートナー株式会社へお任せください！

Page Load Speed

8.4 sec in total

First Response

521 ms

Resources Loaded

5.1 sec

Page Rendered

2.8 sec

find-a.jp screenshot

About Website

Visit find-a.jp now to see the best up-to-date Find A content for Japan and also check out these interesting facts you probably never knew about find-a.jp

SEOサービス Find-Aは、検索意図に応えるコンテンツを制作し、上位表示と集客支援を行う、コンテンツSEOサービスです。2万社以上のお客様にご利用いただいた信頼と実績があります！圧倒的ノウハウのSEOサービスはFind-A(ファインドエー)

Visit find-a.jp

Key Findings

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

Performance Metrics

find-a.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

find-a.jp

521 ms

find-a.jp

750 ms

style.css

167 ms

all.css

49 ms

css2

53 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 81% of them (95 requests) were addressed to the original Find-a.jp, 7% (8 requests) were made to Cache.img.gmo.jp and 3% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Find-a.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.4 kB (9%)

Content Size

3.3 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Find-a.jp main page is 3.3 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. 70% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 65.9 kB

  • Original 78.2 kB
  • After minification 51.1 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 27.1 kB, which is 35% 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 65.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 187.2 kB

  • Original 3.1 MB
  • After minification 2.9 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. Find A images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 36.5 kB

  • Original 73.0 kB
  • After minification 73.0 kB
  • After compression 36.5 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 36.5 kB or 50% of the original size.

CSS Optimization

-11%

Potential reduce by 2.9 kB

  • Original 25.9 kB
  • After minification 25.9 kB
  • After compression 23.1 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. Find-a.jp needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (13%)

Requests Now

111

After Optimization

97

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

find-a.jp

find-a.jp

521 ms

find-a.jp

find-a.jp

750 ms

style.css

style.css

167 ms

all.css

all.css

49 ms

css2

css2

53 ms

js

js

77 ms

script.min.js

script.min.js

114 ms

script.min.js

script.min.js

115 ms

jquery-min.js

jquery-min.js

504 ms

jquery.mousewheel.js

jquery.mousewheel.js

638 ms

script.js

script.js

643 ms

css_browser_selector.js

css_browser_selector.js

638 ms

siteseal.js

siteseal.js

786 ms

js

js

227 ms

analytics.js

analytics.js

32 ms

ie-block.png

ie-block.png

967 ms

find-a-logo.png

find-a-logo.png

481 ms

sp-home.png

sp-home.png

611 ms

sp-tell.png

sp-tell.png

611 ms

sp-mail.png

sp-mail.png

612 ms

sp-corporate.png

sp-corporate.png

623 ms

sp-icon-bg.png

sp-icon-bg.png

660 ms

fv-img.png

fv-img.png

1577 ms

fv01.png

fv01.png

761 ms

fv02.png

fv02.png

779 ms

fv03.png

fv03.png

796 ms

s01-bg-link.png

s01-bg-link.png

803 ms

s01-bg.png

s01-bg.png

1252 ms

s01-b1.png

s01-b1.png

950 ms

s01-b2.png

s01-b2.png

970 ms

s01-b3.png

s01-b3.png

966 ms

s03-1.png

s03-1.png

1461 ms

s03-2.png

s03-2.png

1314 ms

s03-3.png

s03-3.png

1293 ms

s04-bg-link.png

s04-bg-link.png

1145 ms

s04-bg.png

s04-bg.png

1667 ms

s04-b1.png

s04-b1.png

1415 ms

s05-img.png

s05-img.png

1457 ms

s06-01.png

s06-01.png

1489 ms

s06-deco1.png

s06-deco1.png

1579 ms

s06-02.png

s06-02.png

1622 ms

s06-deco2.png

s06-deco2.png

1632 ms

s06-03.png

s06-03.png

1664 ms

s06-deco3.png

s06-deco3.png

1738 ms

s07-arrow1.png

s07-arrow1.png

1742 ms

s07-01.png

s07-01.png

1785 ms

s07-deco1.png

s07-deco1.png

1799 ms

collect

collect

76 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75vY0rw_mMI.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75vY0rw_mMI.ttf

378 ms

fa-solid-900.woff

fa-solid-900.woff

70 ms

fa-regular-400.woff

fa-regular-400.woff

99 ms

u-440qyriQwlOrhSvowK_l5OeyxLV-c.ttf

u-440qyriQwlOrhSvowK_l5OeyxLV-c.ttf

326 ms

collect

collect

48 ms

s07-arrow2.png

s07-arrow2.png

1535 ms

ga-audiences

ga-audiences

106 ms

s07-02.png

s07-02.png

1413 ms

s07-deco2.png

s07-deco2.png

1473 ms

s07-arrow3.png

s07-arrow3.png

1463 ms

lW-qwjwOK3Ps5GSJlNNkMalnrxShJj4wo7AR-pHveD09L4KZAyOA3A.ttf

lW-qwjwOK3Ps5GSJlNNkMalnrxShJj4wo7AR-pHveD09L4KZAyOA3A.ttf

54 ms

s07-03.png

s07-03.png

1473 ms

mieruca-hm.js

mieruca-hm.js

18 ms

s07-deco3.png

s07-deco3.png

1367 ms

s07-arrow4.png

s07-arrow4.png

1407 ms

s07-04.png

s07-04.png

1581 ms

s07-deco4.png

s07-deco4.png

1447 ms

style.css

style.css

9 ms

style.css

style.css

12 ms

gmologo.svg

gmologo.svg

9 ms

weare_gmointernetgroup_member.svg

weare_gmointernetgroup_member.svg

10 ms

s08-1.jpg

s08-1.jpg

1413 ms

logo-gmo28th.svg

logo-gmo28th.svg

8 ms

logo-sdgs.svg

logo-sdgs.svg

11 ms

s08-no01.png

s08-no01.png

1355 ms

s08-txt01.png

s08-txt01.png

1369 ms

s08-3.jpg

s08-3.jpg

1396 ms

s08-no02.png

s08-no02.png

1429 ms

s08-txt03.png

s08-txt03.png

1287 ms

s08-2.jpg

s08-2.jpg

1316 ms

s08-no03.png

s08-no03.png

1352 ms

s08-txt02.png

s08-txt02.png

1396 ms

s08-4.jpg

s08-4.jpg

1223 ms

s08-no04.png

s08-no04.png

1142 ms

s08-txt04.png

s08-txt04.png

1106 ms

s08-5.jpg

s08-5.jpg

1129 ms

s08-no05.png

s08-no05.png

1074 ms

s08-txt05.png

s08-txt05.png

1082 ms

s08-6.jpg

s08-6.jpg

1081 ms

s08-no06.png

s08-no06.png

1067 ms

s08-txt06.png

s08-txt06.png

987 ms

s08-7.jpg

s08-7.jpg

1028 ms

s08-no07.png

s08-no07.png

1037 ms

s08-txt07.png

s08-txt07.png

1082 ms

percent-mouth-o.png

percent-mouth-o.png

1052 ms

meter2-bg.png

meter2-bg.png

1053 ms

meter-bg.png

meter-bg.png

987 ms

interview04.jpg

interview04.jpg

1030 ms

interview06.jpg

interview06.jpg

1044 ms

interview07.jpg

interview07.jpg

1086 ms

interview17.jpg

interview17.jpg

1051 ms

interview18.jpg

interview18.jpg

1041 ms

interview25.jpg

interview25.jpg

988 ms

interview23.jpg

interview23.jpg

1029 ms

interview24.jpg

interview24.jpg

1052 ms

interview34.jpg

interview34.jpg

1073 ms

interview35.jpg

interview35.jpg

1048 ms

interview36.jpg

interview36.jpg

989 ms

interview37.jpg

interview37.jpg

998 ms

interview38.jpg

interview38.jpg

987 ms

interview39.jpg

interview39.jpg

1198 ms

interview40.jpg

interview40.jpg

1021 ms

interview41.jpg

interview41.jpg

1191 ms

interview42.jpg

interview42.jpg

1008 ms

interview43.jpg

interview43.jpg

1009 ms

interview44.jpg

interview44.jpg

1150 ms

interview45.jpg

interview45.jpg

1058 ms

interview-img.png

interview-img.png

1049 ms

overview-img.png

overview-img.png

1054 ms

find-a.jp

find-a.jp

1180 ms

Accessibility Review

find-a.jp accessibility score

79

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

find-a.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

find-a.jp SEO score

83

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

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

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 Find-a.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 Find-a.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

find-a.jp

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