Tools & Wizards About Us
toky.co screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

toky.co

Toky: Business Phone System & Integrated VoIP Service

Page Load Speed

775 ms in total

First Response

15 ms

Resources Loaded

459 ms

Page Rendered

301 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 15 ms and then it took 760 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

toky.co performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value11,880 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

toky.co

15 ms

en

27 ms

toky.css

23 ms

logo.svg

52 ms

browser-web.png

73 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 75% of them (43 requests) were addressed to the original Toky.co, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (185 ms) relates to the external source Cdn.mxpnl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 338.4 kB (37%)

Content Size

903.5 kB

After Optimization

565.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 23.0 kB

  • Original 29.2 kB
  • After minification 24.4 kB
  • After compression 6.2 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 4.9 kB, which is 17% 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 23.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 19.9 kB

  • Original 446.4 kB
  • After minification 426.5 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

-44%

Potential reduce by 77.1 kB

  • Original 175.1 kB
  • After minification 150.2 kB
  • After compression 98.0 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 77.1 kB or 44% of the original size.

CSS Optimization

-86%

Potential reduce by 218.4 kB

  • Original 252.8 kB
  • After minification 252.6 kB
  • After compression 34.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 218.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (47%)

Requests Now

49

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 49 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 24 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

toky.co

toky.co

15 ms

en

en

27 ms

toky.css

toky.css

23 ms

logo.svg

logo.svg

52 ms

browser-web.png

browser-web.png

73 ms

browser-toky.png

browser-toky.png

61 ms

browser-facebook.png

browser-facebook.png

73 ms

worldwide.svg

worldwide.svg

61 ms

toky-all.js

toky-all.js

80 ms

jquery.min.js

jquery.min.js

145 ms

wow.min.js

wow.min.js

67 ms

jquery.foggy.min.js

jquery.foggy.min.js

68 ms

video.js

video.js

68 ms

tooltip.js

tooltip.js

69 ms

affix.js

affix.js

71 ms

alert.js

alert.js

69 ms

button.js

button.js

69 ms

carousel.js

carousel.js

72 ms

collapse.js

collapse.js

70 ms

dropdown.js

dropdown.js

71 ms

modal.js

modal.js

72 ms

popover.js

popover.js

70 ms

scrollspy.js

scrollspy.js

71 ms

tab.js

tab.js

76 ms

transition.js

transition.js

73 ms

bowser.min.js

bowser.min.js

70 ms

script.js

script.js

76 ms

lang.js

lang.js

76 ms

main.js

main.js

76 ms

animate.css

animate.css

76 ms

css

css

116 ms

multiplatform.svg

multiplatform.svg

85 ms

share.svg

share.svg

78 ms

chart.png

chart.png

91 ms

face1.png

face1.png

91 ms

face2.png

face2.png

92 ms

face3.png

face3.png

95 ms

face4.png

face4.png

98 ms

logo-f.svg

logo-f.svg

92 ms

main-pattern.png

main-pattern.png

70 ms

gradient-lines.png

gradient-lines.png

69 ms

play-video-on.png

play-video-on.png

66 ms

play-video.png

play-video.png

58 ms

flags.png

flags.png

42 ms

jquery.min.js

jquery.min.js

151 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

185 ms

analytics.js

analytics.js

120 ms

play.png

play.png

18 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

82 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

93 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

106 ms

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

PRmiXeptR36kaC0GEAetxh_xHqYgAV9Bl_ZQbYUxnQU.woff

126 ms

fontello.woff

fontello.woff

16 ms

44 ms

45 ms

collect

collect

26 ms

collect

collect

56 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

91

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

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

    EN

  • 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 it matches the claimed language. 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: