4.8 sec in total
1 sec
3.6 sec
153 ms
Welcome to sendfile.jp homepage info - get ready to check Send File best content for Japan right away, or after learning these important things about sendfile.jp
ファイルを安全・確実に送受信。送受信の記録を管理できる管理機能も標準装備。個人情報漏洩のリスク対策に。
Visit sendfile.jpWe analyzed Sendfile.jp page load time and found that the first response time was 1 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
sendfile.jp performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value6.1 s
12/100
25%
Value5.7 s
51/100
10%
Value30 ms
100/100
30%
Value0.141
79/100
15%
Value4.3 s
85/100
10%
1018 ms
349 ms
363 ms
363 ms
557 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 96% of them (55 requests) were addressed to the original Sendfile.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Sendfile.jp.
Page size can be reduced by 24.9 kB (18%)
135.1 kB
110.3 kB
In fact, the total size of Sendfile.jp main page is 135.1 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. Images take 94.8 kB which makes up the majority of the site volume.
Potential reduce by 6.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 6.6 kB or 62% of the original size.
Potential reduce by 26 B
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. Send File images are well optimized though.
Potential reduce by 5.7 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 5.7 kB or 41% of the original size.
Potential reduce by 12.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. Sendfile.jp needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 78% of the original size.
Number of requests can be reduced by 22 (39%)
56
34
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Send File. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
sendfile.jp
1018 ms
default.css
349 ms
smooth.pack.js
363 ms
smartMenu.js
363 ms
heightLine.js
557 ms
reset.css
175 ms
modules.css
187 ms
theme.css
592 ms
urchin.js
17 ms
topimage_bg.jpg
722 ms
logo.gif
182 ms
btn_login.gif
175 ms
menu_home.gif
182 ms
menu_contact.gif
187 ms
menu_sitemap.gif
174 ms
topimage.jpg
1035 ms
menu_bg.jpg
520 ms
menu_intro_off.jpg
361 ms
menu_about_off.jpg
362 ms
menu_charge_off.jpg
372 ms
menu_order_off.jpg
543 ms
menu_faq_off.jpg
542 ms
reason_bg.gif
743 ms
reason_title_bg.gif
694 ms
reason_title.gif
722 ms
reason_1_bg.gif
722 ms
reason_1.gif
867 ms
point_g.gif
899 ms
reason_2_bg.gif
903 ms
reason_2.gif
904 ms
reason_3_bg.gif
927 ms
reason_3.gif
1040 ms
reason_4_bg.gif
1078 ms
reason_4.gif
1082 ms
ban_mailproblem.jpg
1622 ms
ban_it.gif
1112 ms
ban_course.gif
1205 ms
ban_none.gif
1212 ms
bar_topics.gif
1258 ms
bar_newsrelease.gif
1261 ms
blank.gif
1297 ms
user_login.gif
1376 ms
btn_login2.gif
1385 ms
btn_order.jpg
1438 ms
__utm.gif
9 ms
award.gif
1390 ms
point_bw.gif
1316 ms
check-trouble.gif
1380 ms
ok.gif
1386 ms
maintenance.gif
1444 ms
ct2_115.jpg
1621 ms
23470001_03_100_JP.gif
1312 ms
pr.gif
1364 ms
0117.gif
1366 ms
up.gif
1285 ms
sitc.gif
1263 ms
print.css
182 ms
sendfile.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
sendfile.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
sendfile.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sendfile.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Sendfile.jp main page’s claimed encoding is euc-jp. 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.
sendfile.jp
Open Graph description is not detected on the main page of Send File. 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: