Tools & Wizards About Us
azflorist.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

azflorist.com

Flower Shop in Phoenix | Arizona Florist

Page Load Speed

4.4 sec in total

First Response

117 ms

Resources Loaded

2.7 sec

Page Rendered

1.6 sec

azflorist.com screenshot

About Website

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

For hand-crafted floral gifts at great prices, turn to Arizona Florist! Our flower shop in Phoenix is here to provide the perfect floral arrangement.

Visit azflorist.com

Key Findings

We analyzed Azflorist.com page load time and found that the first response time was 117 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

azflorist.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value3,610 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.237

52/100

15%

TTI (Time to Interactive)

Value31.4 s

0/100

10%

Network Requests Diagram

azflorist.com

117 ms

azflorist.com

470 ms

theme-bundle.polyfills.js

70 ms

theme-bundle.head_async.js

136 ms

css

77 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 9% of them (12 requests) were addressed to the original Azflorist.com, 35% (49 requests) were made to Fonts.googleapis.com and 22% (31 requests) were made to Cdn11.bigcommerce.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (33%)

Content Size

5.0 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Azflorist.com main page is 5.0 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. Only a small number of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 257.8 kB

  • Original 292.7 kB
  • After minification 241.3 kB
  • After compression 34.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. This page needs HTML code to be minified as it can gain 51.4 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 257.8 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 84 B

  • Original 2.8 MB
  • After minification 2.8 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. Az Florist images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.1 MB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 402.9 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 1.1 MB or 73% of the original size.

CSS Optimization

-91%

Potential reduce by 284.6 kB

  • Original 313.8 kB
  • After minification 226.4 kB
  • After compression 29.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. Azflorist.com needs all CSS files to be minified and compressed as it can save up to 284.6 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 96 (75%)

Requests Now

128

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

azflorist.com

azflorist.com

117 ms

azflorist.com

azflorist.com

470 ms

theme-bundle.polyfills.js

theme-bundle.polyfills.js

70 ms

theme-bundle.head_async.js

theme-bundle.head_async.js

136 ms

css

css

77 ms

theme-bundle.font.js

theme-bundle.font.js

136 ms

theme-880f6610-42d0-013d-4b51-167bf505fa32.css

theme-880f6610-42d0-013d-4b51-167bf505fa32.css

86 ms

google_analytics4-9a468da7c21d2e9e41cd445d567f3f3a5a9b6759.js

google_analytics4-9a468da7c21d2e9e41cd445d567f3f3a5a9b6759.js

78 ms

loader.js

loader.js

138 ms

index.js

index.js

140 ms

element.js

element.js

148 ms

theme-bundle.main.js

theme-bundle.main.js

117 ms

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

csrf-protection-header-5eeddd5de78d98d146ef4fd71b2aedce4161903e.js

116 ms

visitor_stencil.js

visitor_stencil.js

117 ms

init-popcard.js

init-popcard.js

803 ms

eProduct.js

eProduct.js

804 ms

init-loyalty.js

init-loyalty.js

591 ms

init-elocal.js

init-elocal.js

852 ms

klaviyo.js

klaviyo.js

855 ms

fbevents.js

fbevents.js

777 ms

gtm.js

gtm.js

816 ms

1i2emhd0i

1i2emhd0i

1089 ms

store-image.jpg

store-image.jpg

755 ms

header-logo.png

header-logo.png

732 ms

header-logo_1679506807__49117.original.png

header-logo_1679506807__49117.original.png

732 ms

boftm.png

boftm.png

737 ms

sfotm.png

sfotm.png

733 ms

Autumn_Air__57313.1725135363.png

Autumn_Air__57313.1725135363.png

765 ms

5db2c092-b7af-40b1-8357-35df2c34db4d__35762.1725070019.png

5db2c092-b7af-40b1-8357-35df2c34db4d__35762.1725070019.png

765 ms

4f8c4408-89b3-4dc9-b951-9dc32ce979e2__43505.1725065505.png

4f8c4408-89b3-4dc9-b951-9dc32ce979e2__43505.1725065505.png

815 ms

f7c492d9-6063-423b-afec-46bfc8454340__99388.1722468396.png

f7c492d9-6063-423b-afec-46bfc8454340__99388.1722468396.png

814 ms

skusku11460268__46078.1722466681.png

skusku11460268__46078.1722466681.png

822 ms

04cdb1cb-a57a-4e2d-9f5c-fdd6657e12d5__58890.1725055714.png

04cdb1cb-a57a-4e2d-9f5c-fdd6657e12d5__58890.1725055714.png

823 ms

Lilies__29332.1722460631.png

Lilies__29332.1722460631.png

1087 ms

Lilies__29332.1722460631.png

Lilies__29332.1722460631.png

830 ms

FB337_ALT_V1_preset_ftd-mx-hero-sv-alt__41246.1722460628.jpg

FB337_ALT_V1_preset_ftd-mx-hero-sv-alt__41246.1722460628.jpg

832 ms

c468e017-75ed-4c3e-99fe-63ef5bf8f4e3__93319.1725054777.png

c468e017-75ed-4c3e-99fe-63ef5bf8f4e3__93319.1725054777.png

1845 ms

37943656-20240827-4877725.png

37943656-20240827-4877725.png

1083 ms

37943655-20240823-2600863.png

37943655-20240823-2600863.png

1083 ms

77834.jpg

77834.jpg

1078 ms

37064563-20240802-2168120.png

37064563-20240802-2168120.png

1081 ms

summer2024.jpeg

summer2024.jpeg

805 ms

mobsummer.jpeg

mobsummer.jpeg

762 ms

trust.png

trust.png

805 ms

best-sellers1.jpg

best-sellers1.jpg

760 ms

birthday-banner1.jpg

birthday-banner1.jpg

761 ms

sympathy-banner1.jpg

sympathy-banner1.jpg

762 ms

romance-banner1.jpg

romance-banner1.jpg

829 ms

footer-logo.png

footer-logo.png

1079 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lP.ttf

359 ms

templatePopCard.e4pq66f70d.js

templatePopCard.e4pq66f70d.js

126 ms

jquery.min.js

jquery.min.js

145 ms

animation.css

animation.css

123 ms

google-fonts.css

google-fonts.css

127 ms

icon

icon

78 ms

popcard.css

popcard.css

136 ms

template.loyalty.e4pq66f70d.js

template.loyalty.e4pq66f70d.js

391 ms

loyalty.css

loyalty.css

388 ms

fa-solid-900.ttf

fa-solid-900.ttf

891 ms

fa-regular-400.ttf

fa-regular-400.ttf

504 ms

fa-light-300.ttf

fa-light-300.ttf

506 ms

fa-thin-100.ttf

fa-thin-100.ttf

507 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

226 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

403 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

404 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

403 ms

fa-sharp-solid-900.ttf

fa-sharp-solid-900.ttf

498 ms

templatesElocal.e4pq66f70d.js

templatesElocal.e4pq66f70d.js

346 ms

elocalStyle.css

elocalStyle.css

351 ms

index.php

index.php

349 ms

css

css

266 ms

css

css

372 ms

css

css

372 ms

css

css

371 ms

css

css

371 ms

css

css

371 ms

css

css

371 ms

css

css

377 ms

css

css

378 ms

css

css

378 ms

css

css

377 ms

css

css

378 ms

css

css

377 ms

css

css

388 ms

css

css

386 ms

css

css

386 ms

css

css

384 ms

css

css

385 ms

css

css

385 ms

css

css

387 ms

css

css

386 ms

css

css

388 ms

css

css

389 ms

css

css

387 ms

css

css

388 ms

css

css

448 ms

css

css

450 ms

css

css

449 ms

css

css

446 ms

css

css

447 ms

css2

css2

448 ms

css2

css2

451 ms

css

css

450 ms

css2

css2

451 ms

css

css

451 ms

css2

css2

452 ms

jquery-ui.min.js

jquery-ui.min.js

296 ms

elocal.e4pq66f70d.min.js

elocal.e4pq66f70d.min.js

307 ms

noty.min.js

noty.min.js

297 ms

popcard.min.js

popcard.min.js

297 ms

embed

embed

331 ms

nobot

nobot

191 ms

css

css

191 ms

loyalty.e4pq66f70d.min.js

loyalty.e4pq66f70d.min.js

108 ms

css

css

90 ms

css2

css2

87 ms

css

css

88 ms

css

css

88 ms

css2

css2

87 ms

css

css

88 ms

css2

css2

84 ms

css

css

84 ms

css2

css2

83 ms

css2

css2

85 ms

js

js

42 ms

search.js

search.js

5 ms

geometry.js

geometry.js

8 ms

main.js

main.js

13 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

53 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

57 ms

twk-event-polyfill.js

twk-event-polyfill.js

59 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

58 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

69 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

60 ms

twk-main.js

twk-main.js

62 ms

twk-vendor.js

twk-vendor.js

66 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

79 ms

twk-chunk-common.js

twk-chunk-common.js

90 ms

twk-runtime.js

twk-runtime.js

70 ms

twk-app.js

twk-app.js

71 ms

Accessibility Review

azflorist.com accessibility score

96

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.

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

azflorist.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

azflorist.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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Azflorist.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 Azflorist.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

azflorist.com

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