Report Summary

  • 89

    Performance

    Renders faster than
    90% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

tocaly.com

Notice for closing of Tocaly Service - Tocaly en updates

Page Load Speed

849 ms in total

First Response

39 ms

Resources Loaded

722 ms

Page Rendered

88 ms

tocaly.com screenshot

About Website

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

 New Thank you for using Tocaly. We regret to inform you that Tocaly will no longer provide its services as of...

Visit tocaly.com

Key Findings

We analyzed Tocaly.com page load time and found that the first response time was 39 ms and then it took 810 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

tocaly.com performance score

89

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

tocaly.com

39 ms

notice-for-closing-of-tocaly-service-280656

69 ms

client.min.js

31 ms

changelog-tailwind-508b_ou9.js

286 ms

client-3cTQ47us.css

289 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 10% of them (1 request) were addressed to the original Tocaly.com, 50% (5 requests) were made to Assets0.headwayapp.co and 20% (2 requests) were made to Cloud.headwayapp.co. The less responsive or slowest element that took the longest time to load (300 ms) relates to the external source Cloud.headwayapp.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 11.9 kB (40%)

Content Size

29.6 kB

After Optimization

17.7 kB

In fact, the total size of Tocaly.com main page is 29.6 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 15.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 11.7 kB

  • Original 15.8 kB
  • After minification 14.9 kB
  • After compression 4.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 11.7 kB or 74% of the original size.

JavaScript Optimization

-5%

Potential reduce by 11 B

  • Original 224 B
  • After minification 224 B
  • After compression 213 B

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

-2%

Potential reduce by 248 B

  • Original 13.6 kB
  • After minification 13.6 kB
  • After compression 13.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. Tocaly.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tocaly. According to our analytics all requests are already optimized.

Accessibility Review

tocaly.com accessibility score

66

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tocaly.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

tocaly.com SEO score

79

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

High

Page is blocked from indexing

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 Tocaly.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 Tocaly.com 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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: