Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

type.jp

転職ならtype-アクセス者数No.1の転職サイト

Page Load Speed

10 sec in total

First Response

774 ms

Resources Loaded

8.8 sec

Page Rendered

462 ms

type.jp screenshot

About Website

Click here to check amazing Type content for Japan. Otherwise, check out these important facts you probably never knew about type.jp

転職なら【type(タイプ)】。ひとつ上の仕事を見つけられる転職サイト。「大手・優良企業」「正社員」「エンジニア」の求人を多数掲載。さらに「AIによる求人提案」や「企業別の面接対策コンテンツ」などで、満足度の高い転職の実現をサポートします。

Visit type.jp

Key Findings

We analyzed Type.jp page load time and found that the first response time was 774 ms and then it took 9.2 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

type.jp performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value19.6 s

0/100

25%

SI (Speed Index)

Value17.4 s

0/100

10%

TBT (Total Blocking Time)

Value7,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.261

47/100

15%

TTI (Time to Interactive)

Value36.7 s

0/100

10%

Network Requests Diagram

type.jp

774 ms

233152853.js

390 ms

base.css

288 ms

layout.css

473 ms

module_aside.css

312 ms

Our browser made a total of 200 requests to load all elements on the main page. We found that 82% of them (163 requests) were addressed to the original Type.jp, 2% (3 requests) were made to Google.com and 2% (3 requests) were made to D3pj3vgx4ijpjx.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Type.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (21%)

Content Size

6.4 MB

After Optimization

5.1 MB

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

HTML Optimization

-83%

Potential reduce by 140.1 kB

  • Original 169.1 kB
  • After minification 138.9 kB
  • After compression 29.0 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 30.1 kB, which is 18% 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 140.1 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 392.5 kB

  • Original 5.2 MB
  • After minification 4.8 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. Type images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 536.5 kB

  • Original 778.7 kB
  • After minification 729.5 kB
  • After compression 242.2 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 536.5 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 248.3 kB

  • Original 283.2 kB
  • After minification 212.8 kB
  • After compression 34.9 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. Type.jp needs all CSS files to be minified and compressed as it can save up to 248.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (49%)

Requests Now

193

After Optimization

98

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

Accessibility Review

type.jp accessibility score

74

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

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

type.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

type.jp SEO score

98

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Type.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 Type.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph data is detected on the main page of Type. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: