Tools & Wizards About Us
teleflora.edgesuite.net screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

teleflora.edgesuite.net

Page Load Speed

687 ms in total

First Response

121 ms

Resources Loaded

488 ms

Page Rendered

78 ms

teleflora.edgesuite.net screenshot

About Website

Welcome to teleflora.edgesuite.net homepage info - get ready to check Teleflora Edgesuite best content for United States right away, or after learning these important things about teleflora.edgesuite.net

Visit teleflora.edgesuite.net

Key Findings

We analyzed Teleflora.edgesuite.net page load time and found that the first response time was 121 ms and then it took 566 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

teleflora.edgesuite.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

teleflora.edgesuite.net

121 ms

constructionnotactive.asp

138 ms

visit_over.jpg

123 ms

visit.jpg

165 ms

top_border.jpg

161 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Teleflora.edgesuite.net, 92% (11 requests) were made to Notactive.telefloristonline.com. The less responsive or slowest element that took the longest time to load (211 ms) relates to the external source Notactive.telefloristonline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.5 kB (13%)

Content Size

174.5 kB

After Optimization

152.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Teleflora.edgesuite.net main page is 174.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. Images take 148.5 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 4.1 kB

  • Original 5.5 kB
  • After minification 5.5 kB
  • After compression 1.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 4.1 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 5.3 kB

  • Original 148.5 kB
  • After minification 143.1 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. Teleflora Edgesuite images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 13.0 kB

  • Original 20.6 kB
  • After minification 18.1 kB
  • After compression 7.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 13.0 kB or 63% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • Images
  • JavaScript

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

Network Requests Diagram

teleflora.edgesuite.net

teleflora.edgesuite.net

121 ms

constructionnotactive.asp

constructionnotactive.asp

138 ms

visit_over.jpg

visit_over.jpg

123 ms

visit.jpg

visit.jpg

165 ms

top_border.jpg

top_border.jpg

161 ms

left_border.jpg

left_border.jpg

123 ms

flower.jpg

flower.jpg

203 ms

faflogo.jpg

faflogo.jpg

167 ms

dod.jpg

dod.jpg

172 ms

s_code_remote.js

s_code_remote.js

211 ms

right_border.jpg

right_border.jpg

203 ms

bottom_border.jpg

bottom_border.jpg

207 ms

Accessibility Review

teleflora.edgesuite.net accessibility score

73

Accessibility Issues

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

Document doesn't have a <title> element

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

teleflora.edgesuite.net best practices score

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

teleflora.edgesuite.net SEO score

58

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teleflora.edgesuite.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Teleflora.edgesuite.net main page’s claimed encoding is . 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

teleflora.edgesuite.net

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