Tools & Wizards About Us
tinkle.co screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tinkle.co

Tinkle | Business Phone System | VoIP & Cloud Phones

Page Load Speed

4.7 sec in total

First Response

573 ms

Resources Loaded

3.5 sec

Page Rendered

551 ms

tinkle.co screenshot

About Website

Click here to check amazing Tinkle content. Otherwise, check out these important facts you probably never knew about tinkle.co

Tinkle is the smarter business phone system. Instantly connect your team with cloud phones. No setup fees, line rentals or contracts.

Visit tinkle.co

Key Findings

We analyzed Tinkle.co page load time and found that the first response time was 573 ms and then it took 4.1 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

tinkle.co performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value17.7 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value3,690 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.4 s

0/100

10%

Network Requests Diagram

www.tinkle.co

573 ms

gtm.js

58 ms

script.js

330 ms

eye.js

160 ms

jquery.min.js

317 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 91% of them (98 requests) were addressed to the original Tinkle.co, 3% (3 requests) were made to Use.fontawesome.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Tinkle.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (43%)

Content Size

2.5 MB

After Optimization

1.4 MB

  • HTML
  • Images

In fact, the total size of Tinkle.co main page is 2.5 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 736.4 kB

  • Original 861.3 kB
  • After minification 850.3 kB
  • After compression 124.9 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 736.4 kB or 86% of the original size.

Image Optimization

-21%

Potential reduce by 331.8 kB

  • Original 1.6 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. Obviously, Tinkle needs image optimization as it can save up to 331.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 59 (65%)

Requests Now

91

After Optimization

32

  • Images
  • JavaScript

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

Network Requests Diagram

www.tinkle.co

www.tinkle.co

573 ms

gtm.js

gtm.js

58 ms

script.js

script.js

330 ms

eye.js

eye.js

160 ms

jquery.min.js

jquery.min.js

317 ms

jquery-migrate.min.js

jquery-migrate.min.js

237 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

333 ms

zxcvbn-async.min.js

zxcvbn-async.min.js

241 ms

smooth-scrollbar.js

smooth-scrollbar.js

333 ms

v4-shims.min.js

v4-shims.min.js

252 ms

wcvat.js

wcvat.js

315 ms

v2.js

v2.js

35 ms

js

js

62 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

260 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

372 ms

wp-polyfill.min.js

wp-polyfill.min.js

405 ms

hooks.min.js

hooks.min.js

406 ms

i18n.min.js

i18n.min.js

405 ms

main.js

main.js

405 ms

wpcf7-redirect-frontend-script.js

wpcf7-redirect-frontend-script.js

404 ms

index.js

index.js

405 ms

front-script.js

front-script.js

490 ms

8458123.js

8458123.js

489 ms

script.js

script.js

499 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

488 ms

add-to-cart.min.js

add-to-cart.min.js

488 ms

js.cookie.min.js

js.cookie.min.js

498 ms

woocommerce.min.js

woocommerce.min.js

561 ms

cart-fragments.min.js

cart-fragments.min.js

562 ms

xoo-aff-js.js

xoo-aff-js.js

558 ms

xoo-el-js.js

xoo-el-js.js

562 ms

password-strength-meter.min.js

password-strength-meter.min.js

560 ms

mailchimp-woocommerce-public.min.js

mailchimp-woocommerce-public.min.js

561 ms

responsive-menu.js

responsive-menu.js

635 ms

jquery.ui.totop.min.js

jquery.ui.totop.min.js

637 ms

woo-module-script.js

woo-module-script.js

639 ms

theme-script.js

theme-script.js

649 ms

vue.min.js

vue.min.js

653 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

653 ms

core.min.js

core.min.js

710 ms

pum-site-scripts.js

pum-site-scripts.js

636 ms

log

log

443 ms

mobile-detect.min.js

mobile-detect.min.js

578 ms

country-select.min.js

country-select.min.js

566 ms

form-render.min.js

form-render.min.js

582 ms

webpack.runtime.min.js

webpack.runtime.min.js

571 ms

frontend-modules.min.js

frontend-modules.min.js

537 ms

waypoints.min.js

waypoints.min.js

540 ms

swiper.min.js

swiper.min.js

624 ms

NEOM_Logo_320x140-054305.png

NEOM_Logo_320x140-054305.png

214 ms

640px-Amazon_Web_Services_Logo.svg.png

640px-Amazon_Web_Services_Logo.svg.png

147 ms

share-link.min.js

share-link.min.js

494 ms

dialog.min.js

dialog.min.js

442 ms

frontend.min.js

frontend.min.js

439 ms

fa-solid-900.woff

fa-solid-900.woff

128 ms

fa-regular-400.woff

fa-regular-400.woff

154 ms

fa-brands-400.woff

fa-brands-400.woff

155 ms

jet-blocks.min.js

jet-blocks.min.js

469 ms

jet-elements.min.js

jet-elements.min.js

474 ms

widgets-scripts.js

widgets-scripts.js

477 ms

jet-tabs-frontend.min.js

jet-tabs-frontend.min.js

499 ms

popperjs.js

popperjs.js

500 ms

tippy-bundle.js

tippy-bundle.js

510 ms

jet-tricks-frontend.js

jet-tricks-frontend.js

492 ms

frontend.min.js

frontend.min.js

492 ms

preloaded-modules.min.js

preloaded-modules.min.js

484 ms

jet-blog.min.js

jet-blog.min.js

483 ms

fa-solid-900.woff

fa-solid-900.woff

578 ms

fa-solid-900.woff

fa-solid-900.woff

684 ms

fa-solid-900.woff

fa-solid-900.woff

474 ms

fa-regular-400.woff

fa-regular-400.woff

488 ms

fa-regular-400.woff

fa-regular-400.woff

487 ms

fa-regular-400.woff

fa-regular-400.woff

514 ms

eicons.woff

eicons.woff

552 ms

fa-brands-400.woff

fa-brands-400.woff

638 ms

logo.svg

logo.svg

176 ms

fa-brands-400.woff

fa-brands-400.woff

570 ms

fa-brands-400.woff

fa-brands-400.woff

591 ms

Easy-Login.ttf

Easy-Login.ttf

486 ms

logo_sm_logo.svg

logo_sm_logo.svg

543 ms

web_samsung_dash-newcolours.png

web_samsung_dash-newcolours.png

570 ms

trustpilot-owh30j60v6qaz9ceqv6qm0krm7mmbykgfed2aek06a.png

trustpilot-owh30j60v6qaz9ceqv6qm0krm7mmbykgfed2aek06a.png

596 ms

web_samsung_dash-newcolours@2x-1024x832.png

web_samsung_dash-newcolours@2x-1024x832.png

555 ms

workanywhere_hipter@2x.png

workanywhere_hipter@2x.png

630 ms

equinox-logo.png

equinox-logo.png

535 ms

laker@0.5x.png

laker@0.5x.png

554 ms

nhs@0.5x.png

nhs@0.5x.png

553 ms

resincoat_logo.png

resincoat_logo.png

587 ms

tinkle_NT_GXV3380_devices.png

tinkle_NT_GXV3380_devices.png

556 ms

logo-app_store-300x107.png

logo-app_store-300x107.png

561 ms

download-android-2-300x89.png

download-android-2-300x89.png

581 ms

download-for-mac-osx-2-524x176-1-300x100.png

download-for-mac-osx-2-524x176-1-300x100.png

573 ms

images-300x89.png

images-300x89.png

680 ms

work_anywhere_greenbeanbag@2x.png

work_anywhere_greenbeanbag@2x.png

558 ms

poly_platinum.png

poly_platinum.png

560 ms

microsoft_PNG.png

microsoft_PNG.png

718 ms

audiocodes_logo.png

audiocodes_logo.png

562 ms

grandstream_reseller.png

grandstream_reseller.png

562 ms

anywhere365-logo.png

anywhere365-logo.png

599 ms

anywhere_nicolson_blue2@2x.png

anywhere_nicolson_blue2@2x.png

537 ms

paypal-2.svg

paypal-2.svg

564 ms

visa.svg

visa.svg

565 ms

mastercard.svg

mastercard.svg

588 ms

american-express.svg

american-express.svg

586 ms

sectigo_trust_seal_sm_2x-e1567511231506.png

sectigo_trust_seal_sm_2x-e1567511231506.png

546 ms

tinkle_icon_orange.svg

tinkle_icon_orange.svg

575 ms

tinkle_icon_white.svg

tinkle_icon_white.svg

551 ms

popup-sidebar.png

popup-sidebar.png

1045 ms

Accessibility Review

tinkle.co accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

High

Some elements have a [tabindex] value greater than 0

Best Practices

tinkle.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tinkle.co SEO score

90

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 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 Tinkle.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 Tinkle.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

tinkle.co

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