Tools & Wizards About Us
tincantalk.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

tincantalk.com

VOIP, Voice Over IP, Phone Service, PBX, Internet Connections

Page Load Speed

1.4 sec in total

First Response

226 ms

Resources Loaded

1 sec

Page Rendered

199 ms

tincantalk.com screenshot

About Website

Welcome to tincantalk.com homepage info - get ready to check Tincantalk best content right away, or after learning these important things about tincantalk.com

Top Rated VOIP Provider of premium and affordable VOIP phone services for business and residential and Internet Connections.

Visit tincantalk.com

Key Findings

We analyzed Tincantalk.com page load time and found that the first response time was 226 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

tincantalk.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

tincantalk.com

226 ms

style.css

115 ms

seal.js

38 ms

valid-html401

29 ms

award.gif

197 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 45% of them (9 requests) were addressed to the original Tincantalk.com, 20% (4 requests) were made to Myvoipprovider.com and 10% (2 requests) were made to Verify.authorize.net. The less responsive or slowest element that took the longest time to load (316 ms) relates to the external source Voipreview.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.2 kB (46%)

Content Size

69.7 kB

After Optimization

37.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tincantalk.com main page is 69.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. Only 10% of websites need less resources to load. HTML takes 36.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 30.6 kB

  • Original 36.6 kB
  • After minification 33.9 kB
  • After compression 6.0 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 30.6 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 614 B

  • Original 13.6 kB
  • After minification 13.0 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. Tincantalk images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 61 B

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

CSS Optimization

-69%

Potential reduce by 914 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 402 B

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. Tincantalk.com needs all CSS files to be minified and compressed as it can save up to 914 B or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (29%)

Requests Now

17

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tincantalk.com

tincantalk.com

226 ms

style.css

style.css

115 ms

seal.js

seal.js

38 ms

valid-html401

valid-html401

29 ms

award.gif

award.gif

197 ms

px10.gif

px10.gif

85 ms

banner-blue.jpg

banner-blue.jpg

64 ms

banner-orange.jpg

banner-orange.jpg

135 ms

banner-green.jpg

banner-green.jpg

135 ms

tx3w.gif

tx3w.gif

155 ms

a.gif

a.gif

157 ms

e911.gif

e911.gif

145 ms

award.gif

award.gif

29 ms

award.gif

award.gif

295 ms

myvoipprovider-award-01.gif

myvoipprovider-award-01.gif

69 ms

secure90x72.gif

secure90x72.gif

7 ms

bestchoice4.gif

bestchoice4.gif

316 ms

ga.js

ga.js

9 ms

__utm.gif

__utm.gif

14 ms

myvoipprovider-award-01.gif

myvoipprovider-award-01.gif

77 ms

Accessibility Review

tincantalk.com accessibility score

65

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.

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

Image elements do not have [alt] attributes

Best Practices

tincantalk.com best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

tincantalk.com SEO score

46

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tincantalk.com 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 Tincantalk.com main page’s claimed encoding is iso-8859-1. 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

tincantalk.com

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