6.7 sec in total
609 ms
5.7 sec
373 ms
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」「スマイルモール」やWebサイト企画・制作などで、規模やマーケットに捉われることなく「良いサービス」「良いプロダクト」を広められるよう支援して参ります。
Visit for-it.co.jpWe analyzed For-it.co.jp page load time and found that the first response time was 609 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
for-it.co.jp performance score
name
value
score
weighting
Value4.6 s
15/100
10%
Value23.6 s
0/100
25%
Value15.0 s
1/100
10%
Value880 ms
33/100
30%
Value0.015
100/100
15%
Value13.7 s
11/100
10%
609 ms
506 ms
338 ms
837 ms
914 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 73% of them (37 requests) were addressed to the original For-it.co.jp, 6% (3 requests) were made to Platform.twitter.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain For-it.co.jp.
Page size can be reduced by 177.1 kB (28%)
639.5 kB
462.4 kB
In fact, the total size of For-it.co.jp main page is 639.5 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. 40% of websites need less resources to load. Images take 431.3 kB which makes up the majority of the site volume.
Potential reduce by 19.5 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 3.0 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 19.5 kB or 74% of the original size.
Potential reduce by 19.4 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. FORiT images are well optimized though.
Potential reduce by 9.6 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 9.6 kB or 33% of the original size.
Potential reduce by 128.5 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 128.5 kB or 84% of the original size.
Number of requests can be reduced by 18 (36%)
50
32
The browser has sent 50 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 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
for-it.co.jp
609 ms
base.css
506 ms
slide_g.css
338 ms
misc.css
837 ms
misc_pc.css
914 ms
jquery.min.js
55 ms
topbtn.js
365 ms
slide_g.js
506 ms
misc.js
669 ms
bg_Header_Footer.gif
309 ms
FORiT_Logo.png
504 ms
linebutton_88x20.png
355 ms
slide_01_951_265.jpg
1338 ms
slide_02_951_265.jpg
1010 ms
slide03_02_950_265.jpg
906 ms
entranceForit02.jpg
697 ms
employee_01.jpg
1158 ms
OfficeView_01.jpg
1180 ms
sampleImg02.jpg
1238 ms
sampleImg03.jpg
1249 ms
sampleImg04.jpg
1340 ms
sampleImg05.jpg
1502 ms
sampleImg06.jpg
1509 ms
logoAfbw_210.png
1572 ms
logoSmw_210.png
1612 ms
logoAfbBlog_210.png
1665 ms
footer_btn_02.png
1685 ms
footer_btn_01.png
1872 ms
footer_btn_04.png
1870 ms
footer_btn_03.png
1902 ms
footer_btn_05.png
1955 ms
all.js
45 ms
bg_Contents.gif
1992 ms
widgets.js
16 ms
fArrow.png
1970 ms
btn_backtoTop.jpg
2161 ms
ga.js
120 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
85 ms
__utm.gif
67 ms
175 ms
xd_arbiter.php
72 ms
xd_arbiter.php
106 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
24 ms
like.php
167 ms
jot
91 ms
U9rHIpG5ERY.js
39 ms
LVx-xkvaJ0b.png
24 ms
misc_sp.css
835 ms
misc_tab.css
835 ms
btnPrev.png
358 ms
btnNext.png
366 ms
for-it.co.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
for-it.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
for-it.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: