Tools & Wizards About Us
indeed.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    56% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

indeed.jp

仕事探し | Indeed (インディード)

Page Load Speed

902 ms in total

First Response

189 ms

Resources Loaded

625 ms

Page Rendered

88 ms

indeed.jp screenshot

About Website

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

Indeed（インディード）では、あなたの次のキャリアを探すためのさまざまな求人情報をまとめて検索できます。求人検索や履歴書、企業クチコミなどのツールであなたの就職活動をサポートします。

Visit indeed.jp

Key Findings

We analyzed Indeed.jp page load time and found that the first response time was 189 ms and then it took 713 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

indeed.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value16,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value24.2 s

0/100

10%

Network Requests Diagram

indeed.jp

189 ms

www.indeed.jp

196 ms

job_search_indeed_ja_JP.png

93 ms

jobsearch-all-compiled_ja_JP.js

56 ms

analytics.js

7 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 27% of them (4 requests) were addressed to the original Indeed.jp, 20% (3 requests) were made to Google-analytics.com and 13% (2 requests) were made to D3fw5vlhllyvee.cloudfront.net. The less responsive or slowest element that took the longest time to load (196 ms) belongs to the original domain Indeed.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.5 kB (62%)

Content Size

542.0 kB

After Optimization

205.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indeed.jp main page is 542.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 484.3 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 17.9 kB

  • Original 26.8 kB
  • After minification 26.6 kB
  • After compression 8.8 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 17.9 kB or 67% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.0 kB
  • After minification 3.0 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. Indeed images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 299.2 kB

  • Original 484.3 kB
  • After minification 484.3 kB
  • After compression 185.1 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 299.2 kB or 62% of the original size.

CSS Optimization

-69%

Potential reduce by 19.3 kB

  • Original 27.9 kB
  • After minification 27.4 kB
  • After compression 8.6 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. Indeed.jp needs all CSS files to be minified and compressed as it can save up to 19.3 kB or 69% of the original size.

Requests Breakdown

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

Requests Now

11

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indeed.jp

indeed.jp

189 ms

www.indeed.jp

www.indeed.jp

196 ms

job_search_indeed_ja_JP.png

job_search_indeed_ja_JP.png

93 ms

jobsearch-all-compiled_ja_JP.js

jobsearch-all-compiled_ja_JP.js

56 ms

analytics.js

analytics.js

7 ms

beacon.js

beacon.js

7 ms

conversion.js

conversion.js

19 ms

linkid.js

linkid.js

8 ms

67 ms

collect

collect

25 ms

collect

collect

91 ms

43 ms

ga-audiences

ga-audiences

27 ms

precache.html

precache.html

81 ms

jobsearch_all.css

jobsearch_all.css

5 ms

Accessibility Review

indeed.jp accessibility score

93

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

indeed.jp SEO score

92

Search Engine Optimization Advices

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

indeed.jp

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