Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

r-agent.com

転職エージェント|転職ならリクルートエージェント

Page Load Speed

12.1 sec in total

First Response

512 ms

Resources Loaded

10.8 sec

Page Rendered

843 ms

r-agent.com screenshot

About Website

Visit r-agent.com now to see the best up-to-date R Agent content for Japan and also check out these interesting facts you probably never knew about r-agent.com

転職エージェントならリクルートエージェント。実績豊富な転職エージェントが、多数の非公開求人からご希望に沿った求人をご紹介、あなたの転職を成功に導きます。

Visit r-agent.com

Key Findings

We analyzed R-agent.com page load time and found that the first response time was 512 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

r-agent.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value6,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

r-agent.com

512 ms

www.r-agent.com

1276 ms

DLPO.js

491 ms

adlpo.js

505 ms

page_summary.js

509 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original R-agent.com, 4% (2 requests) were made to Assets.adobedtm.com and 4% (2 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (8.3 sec) belongs to the original domain R-agent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.8 kB (24%)

Content Size

1.6 MB

After Optimization

1.2 MB

In fact, the total size of R-agent.com main page is 1.6 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. 35% of websites need less resources to load. Images take 824.8 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 252.4 kB

  • Original 321.1 kB
  • After minification 318.8 kB
  • After compression 68.6 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 252.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 824.8 kB
  • After minification 824.8 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. R Agent images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 142.4 kB

  • Original 495.9 kB
  • After minification 495.8 kB
  • After compression 353.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 142.4 kB or 29% of the original size.

Requests Breakdown

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

Requests Now

49

After Optimization

37

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

Accessibility Review

r-agent.com accessibility score

58

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

High

Image elements do not have [alt] attributes

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.

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

r-agent.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

r-agent.com SEO score

86

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 R-agent.com 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 R-agent.com 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 data is detected on the main page of R Agent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: