Tools & Wizards About Us
tokensya.net screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

tokensya.net

Page Load Speed

4.9 sec in total

First Response

527 ms

Resources Loaded

4 sec

Page Rendered

300 ms

tokensya.net screenshot

About Website

Click here to check amazing Tokensya content. Otherwise, check out these important facts you probably never knew about tokensya.net

ビル清掃、オフィス、店舗の清掃、ビル管理の事なら清掃お任せnetまで。オフィス、マンション、ビル、アパート、店舗、事務所など建物専有部分、共有部分の清掃やビル管理を行っております。床・フロア、カーペットの清掃をご希望のお客様、まずは無料見積りをご利用下さい。

Visit tokensya.net

Key Findings

We analyzed Tokensya.net page load time and found that the first response time was 527 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tokensya.net performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

tokensya.net

527 ms

www.tokensya.net

839 ms

swfobject.js

353 ms

import.css

356 ms

smartRollover.js

373 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 90% of them (57 requests) were addressed to the original Tokensya.net, 10% (6 requests) were made to Emono1.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tokensya.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.0 kB (32%)

Content Size

348.5 kB

After Optimization

237.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokensya.net main page is 348.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. 25% of websites need less resources to load. Images take 216.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.5 kB

  • Original 30.2 kB
  • After minification 26.5 kB
  • After compression 7.7 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.7 kB, which is 12% 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 22.5 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 2.1 kB

  • Original 216.1 kB
  • After minification 213.9 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. Tokensya images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 6.6 kB

  • Original 10.7 kB
  • After minification 10.5 kB
  • After compression 4.1 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 6.6 kB or 62% of the original size.

CSS Optimization

-87%

Potential reduce by 79.7 kB

  • Original 91.6 kB
  • After minification 70.9 kB
  • After compression 11.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. Tokensya.net needs all CSS files to be minified and compressed as it can save up to 79.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (28%)

Requests Now

61

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokensya. 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 CSS and as a result speed up the page load time.

Network Requests Diagram

tokensya.net

tokensya.net

527 ms

www.tokensya.net

www.tokensya.net

839 ms

swfobject.js

swfobject.js

353 ms

import.css

import.css

356 ms

smartRollover.js

smartRollover.js

373 ms

acc-f.js

acc-f.js

205 ms

js.php

js.php

1070 ms

base.css

base.css

534 ms

nekostyle.css

nekostyle.css

357 ms

contents.css

contents.css

386 ms

20110930133233_photo_9.jpg

20110930133233_photo_9.jpg

518 ms

20100304114016_photo_5.jpg

20100304114016_photo_5.jpg

551 ms

20120829153537_photo_50.jpg

20120829153537_photo_50.jpg

409 ms

body_bg.jpg

body_bg.jpg

740 ms

header_logo.jpg

header_logo.jpg

930 ms

header_info.gif

header_info.gif

762 ms

header_menu_bg.png

header_menu_bg.png

775 ms

header_navi01_off.png

header_navi01_off.png

791 ms

header_navi02_off.png

header_navi02_off.png

796 ms

header_navi03_off.png

header_navi03_off.png

911 ms

header_navi04_off.png

header_navi04_off.png

937 ms

header_navi05_off.png

header_navi05_off.png

956 ms

img01.jpg

img01.jpg

221 ms

title01.gif

title01.gif

223 ms

btn01_off.gif

btn01_off.gif

220 ms

img02.jpg

img02.jpg

219 ms

title02.gif

title02.gif

222 ms

btn02_off.gif

btn02_off.gif

396 ms

img03.jpg

img03.jpg

399 ms

title03.gif

title03.gif

408 ms

btn03_off.gif

btn03_off.gif

407 ms

img04.jpg

img04.jpg

409 ms

text02.gif

text02.gif

407 ms

btn04_off.jpg

btn04_off.jpg

572 ms

img05.jpg

img05.jpg

574 ms

text03.gif

text03.gif

591 ms

side_banner04_off.jpg

side_banner04_off.jpg

970 ms

side_banner07_bt.jpg

side_banner07_bt.jpg

1164 ms

side_logo.gif

side_logo.gif

1080 ms

side_icon.gif

side_icon.gif

1096 ms

side_tel.gif

side_tel.gif

1104 ms

side_title02.gif

side_title02.gif

1128 ms

side_btn02_off.jpg

side_btn02_off.jpg

1154 ms

side_banner08.jpg

side_banner08.jpg

1596 ms

side_banner09.gif

side_banner09.gif

1269 ms

side_banner05.gif

side_banner05.gif

1279 ms

toukensya.gif

toukensya.gif

1309 ms

reform_banner.gif

reform_banner.gif

1339 ms

netten_banner.gif

netten_banner.gif

1893 ms

netten_tokyo_banner.gif

netten_tokyo_banner.gif

1233 ms

warpper_border.gif

warpper_border.gif

1242 ms

h2_01.jpg

h2_01.jpg

373 ms

text.gif

text.gif

373 ms

btn_bg.gif

btn_bg.gif

378 ms

acc_ses_regist.php

acc_ses_regist.php

756 ms

ana.php

ana.php

182 ms

h2_02.jpg

h2_02.jpg

356 ms

h2_03.jpg

h2_03.jpg

356 ms

h2_04.jpg

h2_04.jpg

369 ms

side_title01.gif

side_title01.gif

1089 ms

side_border.gif

side_border.gif

1123 ms

side_btn01_off.jpg

side_btn01_off.jpg

1216 ms

acclog.cgi

acclog.cgi

242 ms

Accessibility Review

tokensya.net accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tokensya.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

tokensya.net SEO score

64

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokensya.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Tokensya.net main page’s claimed encoding is shift_jis. 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.

Social Sharing Optimization

tokensya.net

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