4.2 sec in total
114 ms
2.9 sec
1.2 sec
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.comWe analyzed Azflorist.com page load time and found that the first response time was 114 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
azflorist.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.4 s
20/100
25%
Value7.9 s
22/100
10%
Value2,600 ms
4/100
30%
Value0.19
65/100
15%
Value27.2 s
0/100
10%
114 ms
785 ms
831 ms
113 ms
102 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 10% of them (13 requests) were addressed to the original Azflorist.com, 38% (49 requests) were made to Fonts.googleapis.com and 24% (31 requests) were made to Cdn11.bigcommerce.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cdn11.bigcommerce.com.
Page size can be reduced by 1.7 MB (44%)
3.8 MB
2.1 MB
In fact, the total size of Azflorist.com main page is 3.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. 85% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 255.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 52.6 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 255.9 kB or 88% of the original size.
Potential reduce by 205.9 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. Az Florist images are well optimized though.
Potential reduce by 914.1 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 914.1 kB or 80% of the original size.
Potential reduce by 283.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. Azflorist.com needs all CSS files to be minified and compressed as it can save up to 283.3 kB or 91% of the original size.
Number of requests can be reduced by 82 (71%)
115
33
The browser has sent 115 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 29 to 1 for JavaScripts and from 55 to 1 for CSS and as a result speed up the page load time.
azflorist.com
114 ms
azflorist.com
785 ms
theme-bundle.polyfills.js
831 ms
theme-bundle.head_async.js
113 ms
css
102 ms
theme-bundle.font.js
113 ms
theme-54d44050-8bdc-013c-4b80-1ede2c21228e.css
121 ms
js
168 ms
google_analytics4.js
97 ms
loader.js
112 ms
index.js
153 ms
element.js
161 ms
theme-bundle.main.js
142 ms
csrf-protection-header-95f3d9ac8c049e3ed132c83a168cf1d6a8ed0237.js
102 ms
visitor_stencil.js
136 ms
init-popcard.js
688 ms
eProduct.js
869 ms
init-loyalty.js
688 ms
init-elocal.js
687 ms
rmBcUtils.min.js
88 ms
fbevents.js
693 ms
gtm.js
670 ms
header-logo.png
664 ms
store-image.jpg
763 ms
header-logo_1679506807__49117.original.png
664 ms
Petite_3_Revise_2___51595__49524.1679590095.jpg
679 ms
BF89-11K__06204__16372.1679590058.jpg
679 ms
BF216-11KM__69053__98663.1679590067.jpg
677 ms
BF52-11KM__35162__45864.1679590069.jpg
1010 ms
Best-Day-2-2__53912.1688157184.png
1371 ms
Best-Day-2-2__53912.1688157184.png
1150 ms
Best-Day-2-1__94268.1688157185.png
1221 ms
21R300__38113.1688157181.jpg
997 ms
CGP-2-2__12723.1688155002.png
1564 ms
CGP-2-2__12723.1688155002.png
1426 ms
CGP-2-1__44675.1688155007.png
1632 ms
21R130__13087.1688154995.jpg
1354 ms
BF224-11K_1-D__46357__90201.1679590098.jpg
1425 ms
floers.jpeg
1552 ms
31941861-20240111-8895733.png
1567 ms
31941860-20240110-1682043.png
1630 ms
121916.jpg
1633 ms
nebulawinterfashion.jpg
993 ms
nebmobilwinter.jpg
995 ms
trust.png
759 ms
best-sellers1.jpg
992 ms
birthday-banner1.jpg
993 ms
sympathy-banner1.jpg
994 ms
romance-banner1.jpg
991 ms
footer-logo.png
1211 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lM.woff
553 ms
track.js
178 ms
templatePopCard.e4pq66f70d.js
229 ms
jquery.min.js
251 ms
animation.css
210 ms
google-fonts.css
215 ms
icon
174 ms
popcard.css
548 ms
fa-solid-900.ttf
1003 ms
fa-regular-400.ttf
1051 ms
fa-light-300.ttf
1054 ms
fa-thin-100.ttf
1155 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
522 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
569 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
603 ms
pxiEyp8kv8JHgFVrJJfedA.woff
570 ms
fa-sharp-solid-900.ttf
1054 ms
template.loyalty.e4pq66f70d.js
265 ms
loyalty.css
261 ms
templatesElocal.e4pq66f70d.js
264 ms
elocalStyle.css
365 ms
index.php
382 ms
track.json
387 ms
css
35 ms
css
223 ms
css
242 ms
css
329 ms
css
242 ms
css
241 ms
css
331 ms
css
370 ms
css
378 ms
css
376 ms
css
378 ms
css
378 ms
css
376 ms
css
411 ms
css
412 ms
css
411 ms
css
411 ms
css
411 ms
css
410 ms
css
447 ms
css
447 ms
css
443 ms
css
445 ms
css
444 ms
css
444 ms
css
447 ms
css
449 ms
css
448 ms
css
449 ms
css
448 ms
css2
486 ms
css2
449 ms
css
452 ms
css2
452 ms
css
453 ms
css2
454 ms
embed
597 ms
jquery-ui.min.js
409 ms
elocal.e4pq66f70d.min.js
395 ms
noty.min.js
316 ms
popcard.min.js
358 ms
css
406 ms
css
272 ms
nobot
218 ms
loyalty.e4pq66f70d.min.js
344 ms
css2
221 ms
css
251 ms
css
165 ms
css2
161 ms
css
162 ms
css2
123 ms
css
117 ms
css2
118 ms
css2
118 ms
js
51 ms
azflorist.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
azflorist.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
azflorist.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
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: