7.4 sec in total
2.6 sec
4.3 sec
549 ms
Welcome to flowercitytx.com homepage info - get ready to check Flower City TX best content right away, or after learning these important things about flowercitytx.com
Houston, TX Florist - Flower City & Events Provides Flower Delivery on Stunning Flower Arrangements For All Occasions, Celebrate Florals with Bouquets, Long Stem Roses, Garden Roses, Birthdays, Mother...
Visit flowercitytx.comWe analyzed Flowercitytx.com page load time and found that the first response time was 2.6 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
flowercitytx.com performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value9.0 s
1/100
25%
Value10.4 s
8/100
10%
Value2,100 ms
7/100
30%
Value0.126
83/100
15%
Value17.7 s
4/100
10%
2600 ms
34 ms
57 ms
72 ms
106 ms
Our browser made a total of 212 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Flowercitytx.com, 78% (166 requests) were made to Assets.floranext.com and 21% (45 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Flowercitytx.com.
Page size can be reduced by 186.5 kB (29%)
634.8 kB
448.3 kB
In fact, the total size of Flowercitytx.com main page is 634.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 316.9 kB which makes up the majority of the site volume.
Potential reduce by 172.7 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 43.0 kB, which is 23% 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 172.7 kB or 92% of the original size.
Potential reduce by 12 B
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. Flower City TX images are well optimized though.
Potential reduce by 13.2 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.
Potential reduce by 604 B
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. Flowercitytx.com has all CSS files already compressed.
Number of requests can be reduced by 146 (73%)
200
54
The browser has sent 200 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flower City TX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 147 to 1 for JavaScripts and as a result speed up the page load time.
flowercitytx.com
2600 ms
styles-m.css
34 ms
styles-l.css
57 ms
require.min.js
72 ms
requirejs-min-resolver.min.js
106 ms
mixins.min.js
74 ms
requirejs-config.min.js
77 ms
polyfill.min.js
73 ms
jquery.mobile.custom.min.js
16 ms
common.min.js
20 ms
dataPost.min.js
16 ms
bootstrap.min.js
18 ms
jquery.min.js
25 ms
translate-inline.min.js
33 ms
mage-translation-dictionary.min.js
173 ms
responsive.min.js
154 ms
theme.min.js
134 ms
opensans-400.woff
133 ms
opensans-300.woff
154 ms
opensans-600.woff
171 ms
opensans-700.woff
154 ms
template.min.js
142 ms
confirm.min.js
157 ms
widget.min.js
157 ms
main.min.js
156 ms
bootstrap.min.js
156 ms
domReady.min.js
174 ms
jquery.min.js
174 ms
jquery-migrate.min.js
158 ms
172a8fef-1267-4bfb-afdc-75d7bb18ed04.png.webp
157 ms
logo-basic-floranext-black.webp
62 ms
FLNXT-47.jpg.webp
61 ms
FLNXT-14.jpg.webp
71 ms
wildflowergarden.jpg.webp
71 ms
HW0_372769.jpg.webp
372 ms
HW0_372732.jpg.webp
71 ms
HW0_372707.jpg.webp
367 ms
dreamers-delight.jpg.webp
81 ms
botanical-burst.jpg.webp
82 ms
urban-spring.jpg.webp
79 ms
blooming-rose.jpg.webp
79 ms
natures-bliss.jpg.webp
82 ms
bc1eed2d-cc68-4829-9ff2-df8208081e5f_65caed8e0a18f.jpg.webp
512 ms
ae595488-719b-4f31-875b-f94023779e42_65cae9cbcd254.jpg.webp
517 ms
FLNXT-39.jpg.webp
83 ms
FLNXT-34.jpg.webp
83 ms
FLNXT-27.jpg.webp
102 ms
FLNXT-9.jpg.webp
102 ms
FLNXT-2.jpg.webp
102 ms
mixeddozen.jpg.webp
103 ms
heavenlyhalfdozen.jpg.webp
104 ms
HW0_372781.jpg.webp
512 ms
HW0_372738.jpg.webp
396 ms
HW0_372984.jpg.webp
799 ms
HW0_372939.jpg.webp
752 ms
HW0_372773.jpg.webp
401 ms
HW0_372766.jpg.webp
403 ms
HW0_372760.jpg.webp
755 ms
HW0_372762.jpg.webp
876 ms
HW0_372756.jpg.webp
514 ms
HW0_372794.jpg.webp
893 ms
HW0_372792.jpg.webp
521 ms
HW0_372561.jpg.webp
714 ms
HW0_372710.jpg.webp
1001 ms
HW0_372733.jpg.webp
1121 ms
HW0_372677.jpg.webp
758 ms
Poppins-Regular.woff
65 ms
Poppins-Medium.woff
65 ms
Poppins-Light.woff
78 ms
Poppins-SemiBold.woff
79 ms
flora-base-icons.woff
77 ms
Blank-Theme-Icons.woff
77 ms
translate.min.js
87 ms
smart-keyboard-handler.min.js
88 ms
mage.min.js
89 ms
ie-class-fixer.min.js
87 ms
dialog.min.js
72 ms
jquery-ui.min.js
73 ms
tabs.min.js
81 ms
underscore.min.js
93 ms
matchMedia.min.js
66 ms
modal.min.js
63 ms
knockout.min.js
64 ms
knockout-es5.min.js
76 ms
text.min.js
79 ms
scripts.min.js
83 ms
HW0_372685.jpg.webp
1047 ms
HW0_372687.jpg.webp
743 ms
engine.min.js
79 ms
bootstrap.min.js
74 ms
bootstrap.min.js
79 ms
observable_array.min.js
95 ms
bound-nodes.min.js
89 ms
HW0_372868.jpg.webp
1100 ms
HW0_372684.jpg.webp
881 ms
owl.carousel.min.js
85 ms
HW0_372721.jpg.webp
1179 ms
theperfectdozen.jpg.webp
878 ms
simplysensational.jpg.webp
881 ms
credit_card_payment_accepted.png
1236 ms
button.min.js
41 ms
draggable.min.js
41 ms
position.min.js
43 ms
resizable.min.js
74 ms
key-codes.min.js
69 ms
core.min.js
68 ms
collapsible.min.js
66 ms
knockout-repeat.min.js
50 ms
knockout-fast-foreach.min.js
48 ms
autocomplete.min.js
55 ms
renderer.min.js
52 ms
resizable.min.js
66 ms
i18n.min.js
67 ms
scope.min.js
83 ms
range.min.js
81 ms
mage-init.min.js
103 ms
keyboard.min.js
102 ms
optgroup.min.js
124 ms
after-render.min.js
141 ms
autoselect.min.js
135 ms
datepicker.min.js
163 ms
outer_click.min.js
160 ms
fadeVisible.min.js
192 ms
collapsible.min.js
183 ms
staticChecked.min.js
202 ms
simple-checked.min.js
208 ms
bind-html.min.js
240 ms
tooltip.min.js
225 ms
observable_source.min.js
250 ms
console-logger.min.js
258 ms
wrapper.min.js
266 ms
events.min.js
271 ms
es6-collections.min.js
295 ms
mouse.min.js
284 ms
172a8fef-1267-4bfb-afdc-75d7bb18ed04.png.webp
820 ms
jquery.storageapi.extended.min.js
264 ms
loader.min.js
269 ms
async.min.js
264 ms
registry.min.js
265 ms
slider.min.js
242 ms
main.min.js
202 ms
calendar.min.js
188 ms
moment.min.js
184 ms
class.min.js
93 ms
local.min.js
83 ms
logger.min.js
81 ms
entry-factory.min.js
97 ms
console-output-handler.min.js
108 ms
formatter.min.js
98 ms
message-pool.min.js
100 ms
levels-pool.min.js
96 ms
logger-utils.min.js
113 ms
js-translation.json
90 ms
modal-slide.html
84 ms
modal-custom.html
78 ms
jquery.cookie.min.js
96 ms
jquery.storageapi.min.js
100 ms
modal-popup.html
96 ms
arrays.min.js
71 ms
compare.min.js
73 ms
misc.min.js
96 ms
objects.min.js
90 ms
strings.min.js
97 ms
template.min.js
89 ms
dom-observer.min.js
94 ms
bindings.min.js
117 ms
datepicker.min.js
88 ms
timepicker.min.js
91 ms
entry.min.js
77 ms
FormData.min.js
19 ms
MutationObserver.min.js
37 ms
tooltip.html
20 ms
print.css
17 ms
loader.min.js
20 ms
page-cache.min.js
20 ms
app.min.js
21 ms
form-mini.min.js
21 ms
navigation-menu.min.js
19 ms
validation.min.js
31 ms
trim-input.min.js
34 ms
cookies.min.js
35 ms
section-config.min.js
29 ms
invalidation-processor.min.js
30 ms
customer-data.min.js
26 ms
customer-data-mixin.min.js
51 ms
menu.min.js
30 ms
types.min.js
30 ms
layout.min.js
31 ms
validation.min.js
19 ms
url.min.js
25 ms
storage.min.js
40 ms
element.min.js
38 ms
jquery.validate.min.js
24 ms
minicart.min.js
25 ms
final-price.min.js
21 ms
media.min.js
17 ms
messages.min.js
21 ms
collapsable.min.js
32 ms
storage-manager.min.js
25 ms
reCaptcha.min.js
46 ms
reCaptcha-mixin.min.js
63 ms
links.min.js
39 ms
jquery.metadata.min.js
43 ms
collection.min.js
19 ms
escaper.min.js
41 ms
storage-service.min.js
29 ms
website-rule.min.js
28 ms
registry.min.js
32 ms
ids-storage.min.js
21 ms
data-storage.min.js
23 ms
ids-storage-compare.min.js
23 ms
query-builder.min.js
16 ms
flowercitytx.com accessibility score
flowercitytx.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
flowercitytx.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowercitytx.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 Flowercitytx.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.
flowercitytx.com
Open Graph description is not detected on the main page of Flower City TX. 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: