Report Summary

  • 35

    Performance

    Renders faster than
    54% 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 260.5 kB (8%)

Content Size

3.2 MB

After Optimization

3.0 MB

In fact, the total size of Find-a.jp main page is 3.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. 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

-11%

Potential reduce by 4.6 kB

  • Original 41.1 kB
  • After minification 41.1 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 4.6 kB or 11% 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

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.

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

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: