Tools & Wizards About Us
toky.co screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

toky.co

Toky: Business Phone System & Integrated VoIP Service

Page Load Speed

983 ms in total

First Response

7 ms

Resources Loaded

488 ms

Page Rendered

488 ms

toky.co screenshot

About Website

Visit toky.co now to see the best up-to-date Toky content for Taiwan and also check out these interesting facts you probably never knew about toky.co

Easy to setup. Integrates anywhere. Call & message customers via mobile or desktop apps. All for a fair price.

Visit toky.co

Key Findings

We analyzed Toky.co page load time and found that the first response time was 7 ms and then it took 976 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

toky.co performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

toky.co

7 ms

en

11 ms

toky-system.css

4 ms

css

40 ms

js

173 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 84% of them (90 requests) were addressed to the original Toky.co, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (312 ms) relates to the external source Static.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.1 kB (12%)

Content Size

666.7 kB

After Optimization

588.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Toky.co main page is 666.7 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. 65% of websites need less resources to load. Images take 485.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 38.5 kB

  • Original 47.0 kB
  • After minification 37.3 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 21% 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 38.5 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 20.2 kB

  • Original 485.8 kB
  • After minification 465.6 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. Toky images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 13.7 kB

  • Original 106.8 kB
  • After minification 106.8 kB
  • After compression 93.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 13.7 kB or 13% of the original size.

CSS Optimization

-21%

Potential reduce by 5.7 kB

  • Original 27.1 kB
  • After minification 27.1 kB
  • After compression 21.4 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. Toky.co needs all CSS files to be minified and compressed as it can save up to 5.7 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

99

After Optimization

82

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toky.co

toky.co

7 ms

en

en

11 ms

toky-system.css

toky-system.css

4 ms

css

css

40 ms

js

js

173 ms

build.js

build.js

12 ms

analytics.js

analytics.js

149 ms

tracker.js

tracker.js

186 ms

qevents.js

qevents.js

228 ms

hotjar-1404846.js

hotjar-1404846.js

312 ms

logo--full-white.svg

logo--full-white.svg

125 ms

toky-call-widget

toky-call-widget

184 ms

icon-arrow-down__white.svg

icon-arrow-down__white.svg

122 ms

icon-phone-numbers.svg

icon-phone-numbers.svg

121 ms

icon-ivr.svg

icon-ivr.svg

132 ms

icon-reports.svg

icon-reports.svg

132 ms

icon-web-dialer.svg

icon-web-dialer.svg

134 ms

icon-sms.svg

icon-sms.svg

133 ms

icon-call-monitoring.svg

icon-call-monitoring.svg

135 ms

icon-voicemail-drop.svg

icon-voicemail-drop.svg

140 ms

icon-power-dialer.svg

icon-power-dialer.svg

138 ms

icon-notes.svg

icon-notes.svg

140 ms

icon-ring-strategy.svg

icon-ring-strategy.svg

138 ms

icon-click-to-call.svg

icon-click-to-call.svg

145 ms

icon-speech-to-text.svg

icon-speech-to-text.svg

150 ms

salesforce.svg

salesforce.svg

157 ms

hubspot.svg

hubspot.svg

155 ms

pipedrive.svg

pipedrive.svg

151 ms

infusionsoft.svg

infusionsoft.svg

153 ms

freshsales.svg

freshsales.svg

167 ms

amocrm.svg

amocrm.svg

168 ms

agilecrm.svg

agilecrm.svg

165 ms

vtiger.png

vtiger.png

170 ms

insightly.png

insightly.png

169 ms

zoho.svg

zoho.svg

170 ms

kustomer.svg

kustomer.svg

172 ms

front.svg

front.svg

172 ms

slack.svg

slack.svg

174 ms

zapier.svg

zapier.svg

174 ms

zendesk.svg

zendesk.svg

176 ms

zoho-desk.png

zoho-desk.png

175 ms

wordpress.svg

wordpress.svg

177 ms

messagebird.svg

messagebird.svg

181 ms

icon-compass.svg

icon-compass.svg

180 ms

icon-users.svg

icon-users.svg

179 ms

icon-book-open.svg

icon-book-open.svg

182 ms

icon-chat.svg

icon-chat.svg

181 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

190 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

221 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

243 ms

icon-briefcase.svg

icon-briefcase.svg

120 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

230 ms

collect

collect

34 ms

icon-bookmark.svg

icon-bookmark.svg

69 ms

icon-address.svg

icon-address.svg

67 ms

icon-help.svg

icon-help.svg

63 ms

icon-code.svg

icon-code.svg

61 ms

icon-clipboard.svg

icon-clipboard.svg

62 ms

icon-chart-line.svg

icon-chart-line.svg

65 ms

white-shape.svg

white-shape.svg

62 ms

blue-majesty-textured.svg

blue-majesty-textured.svg

84 ms

toky-phone-system-2.png

toky-phone-system-2.png

118 ms

cabify.svg

cabify.svg

113 ms

homify.svg

homify.svg

109 ms

js

js

108 ms

lamudi.svg

lamudi.svg

100 ms

main.toky-widget.js

main.toky-widget.js

30 ms

clearsale.svg

clearsale.svg

102 ms

wework.svg

wework.svg

97 ms

oyo.svg

oyo.svg

149 ms

gray-shape.svg

gray-shape.svg

146 ms

pv

pv

171 ms

white-textured.svg

white-textured.svg

155 ms

carousel-salesteam.png

carousel-salesteam.png

150 ms

carousel-supportteam.png

carousel-supportteam.png

135 ms

carousel-customers.png

carousel-customers.png

148 ms

feature-cloud_bold.png

feature-cloud_bold.png

149 ms

feature-multiplatform_bold.png

feature-multiplatform_bold.png

148 ms

feature-localized_bold.png

feature-localized_bold.png

148 ms

feature-ivr_bold.png

feature-ivr_bold.png

154 ms

feature-integrations_bold.png

feature-integrations_bold.png

153 ms

feature-monitoring_bold.png

feature-monitoring_bold.png

152 ms

bg-integrations.svg

bg-integrations.svg

150 ms

zendesk-icon.png

zendesk-icon.png

150 ms

zapier-icon.png

zapier-icon.png

149 ms

salesforce-icon.png

salesforce-icon.png

152 ms

zoho-icon.png

zoho-icon.png

150 ms

toky-icon.png

toky-icon.png

147 ms

pipedrive-icon.png

pipedrive-icon.png

145 ms

slack-icon.png

slack-icon.png

144 ms

front-icon.png

front-icon.png

141 ms

amocrm-icon.png

amocrm-icon.png

144 ms

infusionsoft-icon.png

infusionsoft-icon.png

143 ms

hubspot-icon.png

hubspot-icon.png

142 ms

gray-shape_flipped.svg

gray-shape_flipped.svg

146 ms

thrive_ministry.png

thrive_ministry.png

146 ms

covercy.png

covercy.png

142 ms

nooklyn.png

nooklyn.png

139 ms

pixel

pixel

109 ms

blue-city-textured.svg

blue-city-textured.svg

117 ms

logo--white.svg

logo--white.svg

111 ms

flag-eeuu.svg

flag-eeuu.svg

95 ms

icon-twitter.svg

icon-twitter.svg

92 ms

icon-facebook.svg

icon-facebook.svg

93 ms

icon-youtube.svg

icon-youtube.svg

92 ms

icon-email.svg

icon-email.svg

90 ms

modules.8da33a8f469c3b5ffcec.js

modules.8da33a8f469c3b5ffcec.js

64 ms

Accessibility Review

toky.co accessibility score

88

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Links do not have a discernible name

Best Practices

toky.co 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

toky.co SEO score

99

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Toky.co can be misinterpreted by Google and other search engines. Our service has detected that English 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 Toky.co 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

toky.co

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