Tools & Wizards About Us
timetr.ee screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

timetr.ee

TimeTree | An app for easy calendar sharing and communication

Page Load Speed

2.4 sec in total

First Response

459 ms

Resources Loaded

1.7 sec

Page Rendered

242 ms

timetr.ee screenshot

About Website

Visit timetr.ee now to see the best up-to-date Time Tr content for Taiwan and also check out these interesting facts you probably never knew about timetr.ee

TimeTree is a communication app that makes it surprisingly easy to share and coordinate calendars with others. You can share events with family, frien

Visit timetr.ee

Key Findings

We analyzed Timetr.ee page load time and found that the first response time was 459 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

timetr.ee performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

timetr.ee

459 ms

timetr.ee

520 ms

16 ms

dd91b471d3d39d32.css

14 ms

35edc4ccc8f8ac8e.css

45 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Timetr.ee, 69% (22 requests) were made to Timetreeapp.com and 25% (8 requests) were made to Images.ctfassets.net. The less responsive or slowest element that took the longest time to load (520 ms) belongs to the original domain Timetr.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 168.2 kB (32%)

Content Size

524.8 kB

After Optimization

356.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Timetr.ee main page is 524.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. 60% of websites need less resources to load. Javascripts take 324.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 70.9 kB

  • Original 103.0 kB
  • After minification 102.7 kB
  • After compression 32.1 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 70.9 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 790 B

  • Original 324.0 kB
  • After minification 324.0 kB
  • After compression 323.2 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

-99%

Potential reduce by 96.5 kB

  • Original 97.8 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Timetr.ee needs all CSS files to be minified and compressed as it can save up to 96.5 kB or 99% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (62%)

Requests Now

29

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

timetr.ee

timetr.ee

459 ms

timetr.ee

timetr.ee

520 ms

16 ms

dd91b471d3d39d32.css

dd91b471d3d39d32.css

14 ms

35edc4ccc8f8ac8e.css

35edc4ccc8f8ac8e.css

45 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

66 ms

webpack-b2283b6f5b234d19.js

webpack-b2283b6f5b234d19.js

65 ms

framework-dab82874eb842bd1.js

framework-dab82874eb842bd1.js

80 ms

main-b714afbb0413af5b.js

main-b714afbb0413af5b.js

86 ms

_app-2fa9808f802e34e3.js

_app-2fa9808f802e34e3.js

87 ms

81cbe537-48438067b286922d.js

81cbe537-48438067b286922d.js

89 ms

6618-81fa03f86b82b46c.js

6618-81fa03f86b82b46c.js

88 ms

5931-9844a53e706da6a8.js

5931-9844a53e706da6a8.js

87 ms

8821-490b11fa7ce8af71.js

8821-490b11fa7ce8af71.js

94 ms

5123-950e18f319c6d6c5.js

5123-950e18f319c6d6c5.js

90 ms

3781-64e9cf8c38830859.js

3781-64e9cf8c38830859.js

94 ms

1959-7f3f1c54ebef424d.js

1959-7f3f1c54ebef424d.js

89 ms

6258-8549845fdc2937a0.js

6258-8549845fdc2937a0.js

93 ms

9413-8b95dec5451e74e6.js

9413-8b95dec5451e74e6.js

93 ms

8846-f5e9b60149103bcd.js

8846-f5e9b60149103bcd.js

99 ms

1474-6c37198abdedc3a5.js

1474-6c37198abdedc3a5.js

111 ms

%5B%5B...slug%5D%5D-496a086f9d70135f.js

%5B%5B...slug%5D%5D-496a086f9d70135f.js

98 ms

_buildManifest.js

_buildManifest.js

97 ms

_ssgManifest.js

_ssgManifest.js

97 ms

Asset_110_3x-8.webp

Asset_110_3x-8.webp

98 ms

top_noti_en.jpg

top_noti_en.jpg

109 ms

top_chat_en.png

top_chat_en.png

116 ms

top_multi_en.jpg

top_multi_en.jpg

116 ms

public-calendar-top.png

public-calendar-top.png

116 ms

top_premium_en.jpg

top_premium_en.jpg

114 ms

Asset_56.svg

Asset_56.svg

116 ms

top_tutorial_en.svg

top_tutorial_en.svg

109 ms

Accessibility Review

timetr.ee accessibility score

91

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

timetr.ee best practices score

92

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

SEO Factors

timetr.ee SEO score

92

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

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 Timetr.ee 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 Timetr.ee 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

timetr.ee

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