Tools & Wizards About Us
sanfranciscofloral.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

sanfranciscofloral.com

Fresno Florist | Unique Flowers |Same Day Flower Delivery

Page Load Speed

3 sec in total

First Response

582 ms

Resources Loaded

1.3 sec

Page Rendered

1.1 sec

sanfranciscofloral.com screenshot

About Website

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

Send beautiful flowers directly from a real local florist. Fresh flowers for any occasion, same-day delivery. Serving Fresno, Sanger, Clovis, Caruthers, Kerman

Visit sanfranciscofloral.com

Key Findings

We analyzed Sanfranciscofloral.com page load time and found that the first response time was 582 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

sanfranciscofloral.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,090 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.756

6/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

sanfranciscofloral.com

582 ms

nectar-combined.min.css

44 ms

nectar-combined.min.js

37 ms

email-decode.min.js

23 ms

slick.min.js

34 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Sanfranciscofloral.com, 59% (27 requests) were made to D775ypbe1855i.cloudfront.net and 17% (8 requests) were made to D5a894zvit21j.cloudfront.net. The less responsive or slowest element that took the longest time to load (582 ms) belongs to the original domain Sanfranciscofloral.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.3 kB (4%)

Content Size

2.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sanfranciscofloral.com main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 75.4 kB

  • Original 96.3 kB
  • After minification 89.4 kB
  • After compression 20.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 75.4 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 46.3 kB

  • Original 2.4 MB
  • After minification 2.4 MB

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. Sanfranciscofloral images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 595 B

  • Original 217.2 kB
  • After minification 217.2 kB
  • After compression 216.6 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

-0%

Potential reduce by 0 B

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

Requests Breakdown

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

Requests Now

34

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sanfranciscofloral.com

sanfranciscofloral.com

582 ms

nectar-combined.min.css

nectar-combined.min.css

44 ms

nectar-combined.min.js

nectar-combined.min.js

37 ms

email-decode.min.js

email-decode.min.js

23 ms

slick.min.js

slick.min.js

34 ms

nectar-deferred-combined.min.js

nectar-deferred-combined.min.js

41 ms

a411.js

a411.js

34 ms

ga.js

ga.js

80 ms

sf-logo-2024.png

sf-logo-2024.png

167 ms

webfont.js

webfont.js

165 ms

warning_bar_0000_us.jpg

warning_bar_0000_us.jpg

113 ms

gotflowers-logo-b-and-w.png

gotflowers-logo-b-and-w.png

113 ms

sff-banner.png

sff-banner.png

144 ms

66_1632326484_6584_thumb.jpg

66_1632326484_6584_thumb.jpg

140 ms

sym2.png

sym2.png

147 ms

tha2.jpg

tha2.jpg

142 ms

wed2.png

wed2.png

141 ms

66_1632326507_7098_thumb.jpg

66_1632326507_7098_thumb.jpg

141 ms

66_1632326486_4862_thumb.jpg

66_1632326486_4862_thumb.jpg

142 ms

66_1699385682_7270_thumb.png

66_1699385682_7270_thumb.png

145 ms

66_1632326501_8650_thumb.jpg

66_1632326501_8650_thumb.jpg

144 ms

66_1676301589_7600_thumb.png

66_1676301589_7600_thumb.png

176 ms

66_1676301631_5695_thumb.png

66_1676301631_5695_thumb.png

178 ms

66_1676301677_7259_thumb.png

66_1676301677_7259_thumb.png

175 ms

66_1632326500_9486_thumb.jpg

66_1632326500_9486_thumb.jpg

175 ms

66_1632326485_1991_thumb.jpg

66_1632326485_1991_thumb.jpg

185 ms

66_1632326484_6584_thumb.jpg

66_1632326484_6584_thumb.jpg

177 ms

66_1632326490_5396_thumb.jpg

66_1632326490_5396_thumb.jpg

175 ms

66_1632326497_8461_thumb.jpg

66_1632326497_8461_thumb.jpg

176 ms

66_1581514320_7888_thumb.jpg

66_1581514320_7888_thumb.jpg

179 ms

66_1632326494_2808_thumb.jpg

66_1632326494_2808_thumb.jpg

178 ms

66_1632326485_1353_thumb.jpg

66_1632326485_1353_thumb.jpg

179 ms

66_1676324355_8957_thumb.png

66_1676324355_8957_thumb.png

180 ms

66_1632326488_7235_thumb.jpg

66_1632326488_7235_thumb.jpg

178 ms

66_1632326487_1626_thumb.jpg

66_1632326487_1626_thumb.jpg

180 ms

66_1632326496_2741_thumb.jpg

66_1632326496_2741_thumb.jpg

180 ms

66_1632326502_1450_thumb.jpg

66_1632326502_1450_thumb.jpg

180 ms

66_1699387930_2983_thumb.png

66_1699387930_2983_thumb.png

181 ms

getFeed

getFeed

176 ms

__utm.gif

__utm.gif

32 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

11 ms

css

css

39 ms

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

16 ms

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff

45 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

57 ms

RWmMoKWR9v4ksMfaWd_JN9XFiaIoDmlr.woff

RWmMoKWR9v4ksMfaWd_JN9XFiaIoDmlr.woff

57 ms

Accessibility Review

sanfranciscofloral.com accessibility score

84

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Best Practices

sanfranciscofloral.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

sanfranciscofloral.com SEO score

91

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanfranciscofloral.com 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), while the claimed language is English. Our system also found out that Sanfranciscofloral.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

sanfranciscofloral.com

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