Tools & Wizards About Us
find-a.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

find-a.jp

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

Page Load Speed

8.2 sec in total

First Response

525 ms

Resources Loaded

5.3 sec

Page Rendered

2.4 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 525 ms and then it took 7.7 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

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

find-a.jp

525 ms

find-a.jp

1075 ms

style.css

339 ms

all.css

88 ms

css2

101 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 81% of them (88 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 (2 sec) belongs to the original domain Find-a.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 280.8 kB (10%)

Content Size

2.8 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Find-a.jp main page is 2.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 54.3 kB

  • Original 65.5 kB
  • After minification 46.4 kB
  • After compression 11.2 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 19.0 kB, which is 29% 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 54.3 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 175.0 kB

  • Original 2.6 MB
  • After minification 2.5 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

-40%

Potential reduce by 20.1 kB

  • Original 50.7 kB
  • After minification 40.0 kB
  • After compression 30.6 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 20.1 kB or 40% of the original size.

CSS Optimization

-58%

Potential reduce by 31.4 kB

  • Original 54.4 kB
  • After minification 45.8 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 31.4 kB or 58% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (12%)

Requests Now

103

After Optimization

91

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 103 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 9 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

525 ms

find-a.jp

find-a.jp

1075 ms

style.css

style.css

339 ms

all.css

all.css

88 ms

css2

css2

101 ms

js

js

109 ms

script.min.js

script.min.js

48 ms

script.min.js

script.min.js

49 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

73 ms

jquery.mousewheel.js

jquery.mousewheel.js

553 ms

script.js

script.js

751 ms

css_browser_selector.js

css_browser_selector.js

749 ms

analytics.js

analytics.js

373 ms

ie-block.png

ie-block.png

1045 ms

find-a-logo.png

find-a-logo.png

536 ms

sp-home.png

sp-home.png

708 ms

sp-tell.png

sp-tell.png

709 ms

sp-mail.png

sp-mail.png

706 ms

sp-corporate.png

sp-corporate.png

873 ms

sp-icon-bg.png

sp-icon-bg.png

878 ms

fv-img.png

fv-img.png

1558 ms

fv01.png

fv01.png

883 ms

fv02.png

fv02.png

890 ms

fv03.png

fv03.png

1040 ms

s01-bg-link.png

s01-bg-link.png

1218 ms

s01-bg.png

s01-bg.png

1406 ms

s01-b1.png

s01-b1.png

1069 ms

s01-b2.png

s01-b2.png

1209 ms

s01-b3.png

s01-b3.png

1225 ms

s03-1.png

s03-1.png

1602 ms

s03-2.png

s03-2.png

1715 ms

s03-3.png

s03-3.png

1557 ms

s04-bg-link.png

s04-bg-link.png

1403 ms

s04-bg.png

s04-bg.png

1762 ms

s04-b1.png

s04-b1.png

1574 ms

s05-img.png

s05-img.png

1728 ms

s06-01.png

s06-01.png

1731 ms

s06-deco1.png

s06-deco1.png

1749 ms

s06-02.png

s06-02.png

1779 ms

s06-deco2.png

s06-deco2.png

1883 ms

s06-03.png

s06-03.png

1897 ms

s06-deco3.png

s06-deco3.png

1901 ms

s07-arrow1.png

s07-arrow1.png

1922 ms

s07-01.png

s07-01.png

1940 ms

s07-deco1.png

s07-deco1.png

1957 ms

s07-arrow2.png

s07-arrow2.png

1732 ms

-F6pfjtqLzI2JPCgQBnw7HFQMisq0Q.woff

-F6pfjtqLzI2JPCgQBnw7HFQMisq0Q.woff

105 ms

fa-solid-900.woff

fa-solid-900.woff

50 ms

fa-regular-400.woff

fa-regular-400.woff

61 ms

u-440qyriQwlOrhSvowK_l5OeA.woff

u-440qyriQwlOrhSvowK_l5OeA.woff

105 ms

s07-02.png

s07-02.png

1736 ms

collect

collect

15 ms

collect

collect

158 ms

mieruca-hm.js

mieruca-hm.js

129 ms

s07-deco2.png

s07-deco2.png

1543 ms

s07-arrow3.png

s07-arrow3.png

1568 ms

style.css

style.css

12 ms

style.css

style.css

7 ms

s07-03.png

s07-03.png

1586 ms

ga-audiences

ga-audiences

112 ms

gmologo.svg

gmologo.svg

70 ms

wearegmogroup_code.svg

wearegmogroup_code.svg

24 ms

logo-gmo26th.svg

logo-gmo26th.svg

34 ms

logo-sdgs.svg

logo-sdgs.svg

37 ms

s07-deco3.png

s07-deco3.png

1438 ms

s07-arrow4.png

s07-arrow4.png

1519 ms

s07-04.png

s07-04.png

1537 ms

s07-deco4.png

s07-deco4.png

1377 ms

s08-1.jpg

s08-1.jpg

1399 ms

s08-no01.png

s08-no01.png

1419 ms

s08-txt01.png

s08-txt01.png

1431 ms

s08-3.jpg

s08-3.jpg

1354 ms

s08-no02.png

s08-no02.png

1374 ms

s08-txt03.png

s08-txt03.png

1348 ms

s08-2.jpg

s08-2.jpg

1241 ms

s08-no03.png

s08-no03.png

1262 ms

s08-txt02.png

s08-txt02.png

1275 ms

s08-4.jpg

s08-4.jpg

1159 ms

s08-no04.png

s08-no04.png

1181 ms

s08-txt04.png

s08-txt04.png

1032 ms

s08-5.jpg

s08-5.jpg

1067 ms

s08-no05.png

s08-no05.png

1083 ms

s08-txt05.png

s08-txt05.png

1077 ms

s08-6.jpg

s08-6.jpg

1016 ms

s08-no06.png

s08-no06.png

1028 ms

s08-txt06.png

s08-txt06.png

1027 ms

s08-7.jpg

s08-7.jpg

1048 ms

s08-no07.png

s08-no07.png

1073 ms

s08-txt07.png

s08-txt07.png

1077 ms

s09-01.png

s09-01.png

1183 ms

s09-02.png

s09-02.png

1027 ms

percent-mouth-o.png

percent-mouth-o.png

1027 ms

meter2-bg.png

meter2-bg.png

1049 ms

meter-bg.png

meter-bg.png

1073 ms

interview04.jpg

interview04.jpg

1077 ms

interview05.jpg

interview05.jpg

1046 ms

interview06.jpg

interview06.jpg

1029 ms

interview07.jpg

interview07.jpg

1075 ms

interview17.jpg

interview17.jpg

1094 ms

interview18.jpg

interview18.jpg

1096 ms

interview25.jpg

interview25.jpg

1097 ms

interview23.jpg

interview23.jpg

1049 ms

interview24.jpg

interview24.jpg

1030 ms

interview33.jpg

interview33.jpg

1079 ms

interview34.jpg

interview34.jpg

1099 ms

interview35.jpg

interview35.jpg

1098 ms

interview36.jpg

interview36.jpg

1088 ms

interview-img.png

interview-img.png

1050 ms

overview-img.png

overview-img.png

1030 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

85

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: