Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

teamoflowers.com

Te Amo Flowers – Luxury Flower Experience

Page Load Speed

313 ms in total

First Response

64 ms

Resources Loaded

187 ms

Page Rendered

62 ms

About Website

Click here to check amazing Te Amo Flowers content. Otherwise, check out these important facts you probably never knew about teamoflowers.com

Visit teamoflowers.com

Key Findings

We analyzed Teamoflowers.com page load time and found that the first response time was 64 ms and then it took 249 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. This domain responded with an error, which can significantly jeopardize Teamoflowers.com rating and web reputation

Performance Metrics

teamoflowers.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value6.1 s

64/100

10%

Network Requests Diagram

teamoflowers.com

64 ms

main.css

4 ms

beacon.js

88 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 67% of them (2 requests) were addressed to the original Teamoflowers.com, 33% (1 request) were made to Performance.radar.cloudflare.com. The less responsive or slowest element that took the longest time to load (88 ms) relates to the external source Performance.radar.cloudflare.com.

Page Optimization Overview & Recommendations

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

Content Size

7.5 kB

After Optimization

4.1 kB

In fact, the total size of Teamoflowers.com main page is 7.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 5.3 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 3.4 kB

  • Original 5.3 kB
  • After minification 4.9 kB
  • After compression 1.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 3.4 kB or 65% of the original size.

CSS Optimization

-1%

Potential reduce by 13 B

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

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

Accessibility Review

teamoflowers.com accessibility score

80

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

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

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

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

teamoflowers.com SEO score

93

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teamoflowers.com 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 Teamoflowers.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 description is not detected on the main page of Te Amo Flowers. 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: