Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

telepresence.io

Home | Telepresence

Page Load Speed

1.9 sec in total

First Response

131 ms

Resources Loaded

1.4 sec

Page Rendered

406 ms

telepresence.io screenshot

About Website

Welcome to telepresence.io homepage info - get ready to check Telepresence best content for Turkey right away, or after learning these important things about telepresence.io

Telepresence: a local development environment for a remote Kubernetes cluster

Visit telepresence.io

Key Findings

We analyzed Telepresence.io page load time and found that the first response time was 131 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

telepresence.io performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

Network Requests Diagram

telepresence.io

131 ms

telepresence.io

259 ms

www.telepresence.io

33 ms

gtm.js

54 ms

polyfill-28a590f767c68ce75d26.js

227 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 68% of them (23 requests) were addressed to the original Telepresence.io, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (631 ms) belongs to the original domain Telepresence.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.8 kB (49%)

Content Size

186.8 kB

After Optimization

96.0 kB

In fact, the total size of Telepresence.io main page is 186.8 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. HTML takes 154.6 kB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 88.2 kB

  • Original 154.6 kB
  • After minification 154.6 kB
  • After compression 66.4 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 88.2 kB or 57% of the original size.

Image Optimization

-23%

Potential reduce by 2.6 kB

  • Original 11.2 kB
  • After minification 8.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. Obviously, Telepresence needs image optimization as it can save up to 2.6 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 15 (63%)

Requests Now

24

After Optimization

9

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

Accessibility Review

telepresence.io accessibility score

94

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

Best Practices

telepresence.io 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

Page has valid source maps

SEO Factors

telepresence.io SEO score

100

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

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 Telepresence.io 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 Telepresence.io 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

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