Tools & Wizards About Us
for-it.co.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

for-it.co.jp

株式会社フォーイット FORiT

Page Load Speed

6.9 sec in total

First Response

364 ms

Resources Loaded

6.1 sec

Page Rendered

454 ms

for-it.co.jp screenshot

About Website

Click here to check amazing FORiT content for United States. Otherwise, check out these important facts you probably never knew about for-it.co.jp

株式会社フォーイットは自社開発アフィリエイト・プラットフォーム「afb」「Webrige」やWebサイト企画・制作などで、規模やマーケットに捉われることなく「良いサービス」「良いプロダクト」を広められるよう支援して参ります。

Visit for-it.co.jp

Key Findings

We analyzed For-it.co.jp page load time and found that the first response time was 364 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

for-it.co.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value25.2 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

for-it.co.jp

364 ms

www.for-it.co.jp

1345 ms

gtm.js

72 ms

wp-emoji-release.min.js

478 ms

sb-instagram.min.css

502 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 65% of them (60 requests) were addressed to the original For-it.co.jp, 5% (5 requests) were made to Pro.fontawesome.com and 4% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain For-it.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 610.0 kB (16%)

Content Size

3.7 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of For-it.co.jp main page is 3.7 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 89.0 kB

  • Original 117.8 kB
  • After minification 104.4 kB
  • After compression 28.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 11% 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 89.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 2.6 MB
  • After minification 2.6 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. FORiT images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 487.9 kB

  • Original 940.1 kB
  • After minification 912.0 kB
  • After compression 452.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 487.9 kB or 52% of the original size.

CSS Optimization

-34%

Potential reduce by 31.9 kB

  • Original 93.3 kB
  • After minification 89.0 kB
  • After compression 61.3 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. For-it.co.jp needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (61%)

Requests Now

83

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

for-it.co.jp

for-it.co.jp

364 ms

www.for-it.co.jp

www.for-it.co.jp

1345 ms

gtm.js

gtm.js

72 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

478 ms

sb-instagram.min.css

sb-instagram.min.css

502 ms

font-awesome.min.css

font-awesome.min.css

88 ms

style.css

style.css

521 ms

default.min.css

default.min.css

643 ms

jquery.js

jquery.js

1089 ms

jquery-migrate.min.js

jquery-migrate.min.js

499 ms

style.css

style.css

946 ms

common.css

common.css

663 ms

slick.css

slick.css

984 ms

slick-theme.css

slick-theme.css

687 ms

top.css

top.css

1455 ms

page.css

page.css

1225 ms

page2.css

page2.css

1164 ms

swiper.min.css

swiper.min.css

1166 ms

all.css

all.css

89 ms

adsbygoogle.js

adsbygoogle.js

133 ms

jquery.min.js

jquery.min.js

39 ms

velocity.js

velocity.js

87 ms

picturefill.js

picturefill.js

1302 ms

swiper.min.js

swiper.min.js

1911 ms

slick.min.js

slick.min.js

1666 ms

page.js

page.js

1342 ms

plx.js

plx.js

1384 ms

transitionanimate.js

transitionanimate.js

1550 ms

common.js

common.js

1549 ms

jquery.inview.min.js

jquery.inview.min.js

1639 ms

sb-instagram.min.js

sb-instagram.min.js

1818 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

1708 ms

global.js

global.js

1708 ms

jquery.scrollTo.js

jquery.scrollTo.js

1734 ms

wp-embed.min.js

wp-embed.min.js

2034 ms

js

js

61 ms

analytics.js

analytics.js

18 ms

collect

collect

13 ms

collect

collect

108 ms

ga-audiences

ga-audiences

48 ms

slotcar_library.js

slotcar_library.js

84 ms

show_ads_impl.js

show_ads_impl.js

248 ms

2SQZ8-TB8UC-9WVJX-N4XUH-ZEYH4

2SQZ8-TB8UC-9WVJX-N4XUH-ZEYH4

210 ms

header_logo.png

header_logo.png

424 ms

nav_off.png

nav_off.png

408 ms

nav_on.png

nav_on.png

431 ms

sp_mv_text.png

sp_mv_text.png

543 ms

interview_designer.webp

interview_designer.webp

728 ms

wantedly.png

wantedly.png

606 ms

external-link-solid.png

external-link-solid.png

605 ms

interview_grobal3.png

interview_grobal3.png

1092 ms

interview_grobal1.png

interview_grobal1.png

1021 ms

img_01.png

img_01.png

1101 ms

img_02.png

img_02.png

1392 ms

img_03.png

img_03.png

1373 ms

1.jpg

1.jpg

948 ms

2.jpg

2.jpg

1260 ms

7.jpg

7.jpg

1195 ms

3.jpg

3.jpg

1323 ms

6.jpg

6.jpg

1285 ms

slider_arrow_left.jpg

slider_arrow_left.jpg

1361 ms

slider_arrow_right.jpg

slider_arrow_right.jpg

1473 ms

recruit_img.png

recruit_img.png

1520 ms

recruit_btn_01.jpg

recruit_btn_01.jpg

1522 ms

recruit_btn_02.jpg

recruit_btn_02.jpg

1604 ms

recruit_btn_03.jpg

recruit_btn_03.jpg

1545 ms

recruit_btn_04.png

recruit_btn_04.png

1579 ms

recruit_btn_05.png

recruit_btn_05.png

1784 ms

recruit_btn_06.png

recruit_btn_06.png

1678 ms

fa-solid-900.woff

fa-solid-900.woff

121 ms

fa-regular-400.woff

fa-regular-400.woff

166 ms

fa-light-300.woff

fa-light-300.woff

161 ms

fa-brands-400.woff

fa-brands-400.woff

136 ms

img_office.jpg

img_office.jpg

1690 ms

pagetop.png

pagetop.png

1629 ms

zrt_lookup.html

zrt_lookup.html

163 ms

ads

ads

203 ms

bnr_wantedly_1.jpg

bnr_wantedly_1.jpg

1619 ms

footer_logo.png

footer_logo.png

1599 ms

config.json

config.json

52 ms

mv_text.png

mv_text.png

1636 ms

8ysicdm3t3

8ysicdm3t3

60 ms

540801ed.js

540801ed.js

745 ms

uh.js

uh.js

695 ms

1c9d747e-050e-4da4-b642-00cf70dbc213.js

1c9d747e-050e-4da4-b642-00cf70dbc213.js

48 ms

hm.js

hm.js

201 ms

clarity.js

clarity.js

15 ms

index.js

index.js

714 ms

mieruca-hm.js

mieruca-hm.js

23 ms

sodar

sodar

72 ms

c.gif

c.gif

10 ms

sodar2.js

sodar2.js

16 ms

Accessibility Review

for-it.co.jp accessibility score

56

Accessibility Issues

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.

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

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

for-it.co.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

for-it.co.jp SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 For-it.co.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 For-it.co.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

for-it.co.jp

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