Tools & Wizards About Us
tenso.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

tenso.com

日本の通販商品の海外発送（国際配送）代行サービス【転送コム】

Page Load Speed

4.6 sec in total

First Response

27 ms

Resources Loaded

4.1 sec

Page Rendered

455 ms

tenso.com screenshot

About Website

Welcome to tenso.com homepage info - get ready to check Tenso best content for China right away, or after learning these important things about tenso.com

転送コムは、日本の通販サイトの商品を世界に発送代行するサービスです。業界最安値＆手続き簡単＆登録無料。

Visit tenso.com

Key Findings

We analyzed Tenso.com page load time and found that the first response time was 27 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

tenso.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.229

54/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

www.tenso.com

27 ms

www.tenso.com

30 ms

gtm.js

68 ms

swiper.min.css

1122 ms

font-awesome.min.css

1071 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 81% of them (55 requests) were addressed to the original Tenso.com, 7% (5 requests) were made to Image.tenso.com and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Tenso.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.0 kB (4%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tenso.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. 65% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 64.3 kB

  • Original 83.9 kB
  • After minification 68.0 kB
  • After compression 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 15.9 kB, which is 19% 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 64.3 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 3.3 kB

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

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

  • Original 183.3 kB
  • After minification 183.3 kB
  • After compression 181.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 980 B

  • Original 48.8 kB
  • After minification 48.8 kB
  • After compression 47.8 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. Tenso.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 16 (25%)

Requests Now

63

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tenso.com

www.tenso.com

27 ms

www.tenso.com

www.tenso.com

30 ms

gtm.js

gtm.js

68 ms

swiper.min.css

swiper.min.css

1122 ms

font-awesome.min.css

font-awesome.min.css

1071 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

1066 ms

main.min.css

main.min.css

1836 ms

swiper.min.js

swiper.min.js

1409 ms

moment.min.js

moment.min.js

1262 ms

server_date

server_date

2084 ms

app.js

app.js

2231 ms

common.js

common.js

2011 ms

progress.js

progress.js

1593 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

1760 ms

top.js

top.js

2527 ms

navigation.js

navigation.js

2666 ms

dammy_pc.png

dammy_pc.png

1965 ms

dammy_sp.png

dammy_sp.png

1966 ms

tensocom_servicelogo.png

tensocom_servicelogo.png

1966 ms

icon_step3_customer.png

icon_step3_customer.png

1967 ms

officelady_01.png

officelady_01.png

1968 ms

officelady_02.png

officelady_02.png

1967 ms

officelady_03.png

officelady_03.png

1968 ms

users_case_1_4.jpg

users_case_1_4.jpg

1969 ms

users_case_1_0_face.png

users_case_1_0_face.png

1969 ms

users_case_1_1.jpg

users_case_1_1.jpg

1970 ms

users_case_1_2.jpg

users_case_1_2.jpg

1970 ms

users_case_1_3.jpg

users_case_1_3.jpg

1971 ms

users_case_1_5.jpg

users_case_1_5.jpg

1970 ms

users_case_1_0.jpg

users_case_1_0.jpg

1971 ms

step_num-01.svg

step_num-01.svg

1971 ms

users_case_2_3.jpg

users_case_2_3.jpg

1974 ms

users_case_2_0_face.png

users_case_2_0_face.png

1974 ms

users_case_2_1.jpg

users_case_2_1.jpg

1975 ms

users_case_2_2.jpg

users_case_2_2.jpg

1975 ms

users_case_2_4.jpg

users_case_2_4.jpg

1975 ms

users_case_2_5.jpg

users_case_2_5.jpg

1975 ms

users_case_2_0.jpg

users_case_2_0.jpg

1976 ms

step_num-02.svg

step_num-02.svg

1976 ms

js

js

79 ms

destination

destination

78 ms

analytics.js

analytics.js

24 ms

destination

destination

75 ms

fbevents.js

fbevents.js

72 ms

collect

collect

236 ms

collect

collect

32 ms

users_case_3_4.jpg

users_case_3_4.jpg

924 ms

users_case_3_0_face.png

users_case_3_0_face.png

918 ms

users_case_3_1.jpg

users_case_3_1.jpg

870 ms

users_case_3_2.jpg

users_case_3_2.jpg

727 ms

users_case_3_3.jpg

users_case_3_3.jpg

582 ms

users_case_3_0.jpg

users_case_3_0.jpg

396 ms

step_num-03.svg

step_num-03.svg

231 ms

we_user_01.png

we_user_01.png

27 ms

we_user_02.png

we_user_02.png

26 ms

we_user_03.png

we_user_03.png

27 ms

visual_top_hero_0.jpg

visual_top_hero_0.jpg

1212 ms

visual_top_hero_1.jpg

visual_top_hero_1.jpg

710 ms

icon_all_payments.png

icon_all_payments.png

119 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1713 ms

get_site_banner

get_site_banner

422 ms

get_site_banner

get_site_banner

424 ms

5136704516396b8c1cabb1

5136704516396b8c1cabb1

36 ms

1208824898617a687d525d0

1208824898617a687d525d0

8 ms

17301086805bd155bec80f8

17301086805bd155bec80f8

740 ms

129298272661836c4d74c37

129298272661836c4d74c37

902 ms

18092161775b10b5c0e5d40

18092161775b10b5c0e5d40

20 ms

visual_top_hero_0.jpg

visual_top_hero_0.jpg

5 ms

Accessibility Review

tenso.com accessibility score

80

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

tenso.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tenso.com SEO score

80

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

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 doesn't use 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 Tenso.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 Tenso.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

tenso.com

Open Graph description is not detected on the main page of Tenso. 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: