3.8 sec in total
375 ms
2.4 sec
1 sec
Visit southerngracefloralmarket.com now to see the best up-to-date Southern Grace Floral Market content and also check out these interesting facts you probably never knew about southerngracefloralmarket.com
St Johns, FL Florist: Southern Grace Fresh Floral Market Provides Same Day Flower Delivery On Stunning Flower Arrangements For All Occasions, Celebrate Florals With Bouquets, Long Stem Roses, Garden R...
Visit southerngracefloralmarket.comWe analyzed Southerngracefloralmarket.com page load time and found that the first response time was 375 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
southerngracefloralmarket.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value8.1 s
2/100
25%
Value6.5 s
39/100
10%
Value2,570 ms
4/100
30%
Value0.144
78/100
15%
Value20.7 s
2/100
10%
375 ms
62 ms
82 ms
112 ms
130 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Southerngracefloralmarket.com, 82% (135 requests) were made to Assets.floranext.com and 17% (28 requests) were made to Image.floranext.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Image.floranext.com.
Page size can be reduced by 489.0 kB (17%)
2.8 MB
2.3 MB
In fact, the total size of Southerngracefloralmarket.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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 155.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 23.1 kB, which is 13% 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 155.9 kB or 90% of the original size.
Potential reduce by 322.5 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. Obviously, Southern Grace Floral Market needs image optimization as it can save up to 322.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 721 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. Southerngracefloralmarket.com has all CSS files already compressed.
Number of requests can be reduced by 119 (77%)
155
36
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Southern Grace Floral Market. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 117 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
southerngracefloralmarket.com
375 ms
calendar.css
62 ms
styles-m.css
82 ms
styles-l.css
112 ms
require.min.js
130 ms
requirejs-min-resolver.min.js
110 ms
mixins.min.js
111 ms
requirejs-config.min.js
109 ms
polyfill.min.js
138 ms
untitled_design_11__63b743a4f3fd7.png
90 ms
logo-basic-floranext-black.webp
43 ms
valentines_banner_63ee9511412fd.png.webp
44 ms
screen_shot_2024-02-26_at_1.53.14_pm_65dcde2f0ce9a.png.webp
525 ms
copy_of_flower_subscription_63b7435bddc6e.png.webp
327 ms
img_3824_64c171c381c11.jpg.webp
416 ms
img_3592_64b70fbf56656.jpg.webp
447 ms
img_9556_64062ae16603b.jpg.webp
479 ms
img_4501_jpg_63c07c8ae4768.jpg.webp
441 ms
1ff864d8-3292-49cf-a23d-9338eacc7c44_6299677f9d652.jpg.webp
730 ms
cb76d495-6258-431f-9afd-3a118ce00ead_63ee9677b2812.png.webp
671 ms
321777873_717123836794033_3948290179181899056_n_63f4228de6445.jpg.webp
722 ms
img_5263_1_63bdbef165fe6.jpg.webp
890 ms
img_4676_1_63bdbf52a7a93.jpg.webp
917 ms
img_1942_65bc01db698a6.jpg.webp
804 ms
img_9540_64062a494e284.jpg.webp
873 ms
img_9557_640628857ac73.jpg.webp
1159 ms
img_5128_2_1_63bdbf611e42e.jpg.webp
1157 ms
img_3816_1_63bdbd367469a.jpg.webp
1098 ms
img_3508_1_63bdbe4361e0a.jpg.webp
1118 ms
img_9798_1_63bdbf6748990.jpg.webp
1335 ms
1_63b73d28d6445.png.webp
1406 ms
2_63b73d374a252.png.webp
1475 ms
3_63b73d3f6a039.png.webp
1331 ms
4_63b73d4b5ce35.png.webp
1365 ms
copy_of_copy_of_sgf_facebook_cover_4__63b7363101fc1.png.webp
1494 ms
Review_us_on_GOOGLE_10__639ba7961fdd6.png
1672 ms
Footer_Image_639ba7bb99bdc.png
1496 ms
jquery.mobile.custom.min.js
36 ms
common.min.js
29 ms
dataPost.min.js
29 ms
bootstrap.min.js
29 ms
jquery.min.js
34 ms
translate-inline.min.js
65 ms
mage-translation-dictionary.min.js
61 ms
responsive.min.js
60 ms
theme.min.js
61 ms
opensans-400.woff
119 ms
opensans-300.woff
59 ms
opensans-600.woff
120 ms
opensans-700.woff
121 ms
Lato-Regular.woff
120 ms
domReady.min.js
118 ms
template.min.js
94 ms
confirm.min.js
97 ms
widget.min.js
96 ms
main.min.js
95 ms
bootstrap.min.js
96 ms
jquery.min.js
91 ms
jquery-migrate.min.js
74 ms
owl.carousel.min.js
32 ms
flora-base-icons.woff
33 ms
Blank-Theme-Icons.woff
33 ms
text.min.js
62 ms
tabs.min.js
62 ms
smart-keyboard-handler.min.js
62 ms
mage.min.js
61 ms
ie-class-fixer.min.js
59 ms
translate.min.js
60 ms
underscore.min.js
61 ms
knockout.min.js
57 ms
knockout-es5.min.js
58 ms
matchMedia.min.js
50 ms
dialog.min.js
50 ms
jquery-ui.min.js
47 ms
modal.min.js
49 ms
modal-mixin.min.js
48 ms
scripts.min.js
47 ms
engine.min.js
49 ms
valentines_banner_63ee9511412fd.png.webp
1149 ms
bootstrap.min.js
38 ms
bootstrap.min.js
37 ms
bootstrap.min.js
40 ms
observable_array.min.js
38 ms
bound-nodes.min.js
38 ms
core.min.js
37 ms
collapsible.min.js
34 ms
key-codes.min.js
30 ms
button.min.js
30 ms
draggable.min.js
29 ms
position.min.js
30 ms
resizable.min.js
29 ms
knockout-repeat.min.js
29 ms
knockout-fast-foreach.min.js
34 ms
autocomplete.min.js
48 ms
wrapper.min.js
60 ms
events.min.js
78 ms
es6-collections.min.js
95 ms
format.min.js
109 ms
jqueryTooltip.min.js
126 ms
bootstrap-datepicker.min.js
154 ms
jquery.storageapi.extended.min.js
170 ms
observable_source.min.js
184 ms
renderer.min.js
201 ms
console-logger.min.js
216 ms
resizable.min.js
235 ms
i18n.min.js
250 ms
scope.min.js
263 ms
range.min.js
267 ms
mage-init.min.js
282 ms
keyboard.min.js
285 ms
optgroup.min.js
279 ms
after-render.min.js
279 ms
autoselect.min.js
282 ms
datepicker.min.js
299 ms
outer_click.min.js
292 ms
fadeVisible.min.js
295 ms
collapsible.min.js
294 ms
staticChecked.min.js
296 ms
simple-checked.min.js
303 ms
bind-html.min.js
308 ms
tooltip.min.js
315 ms
color-picker.min.js
309 ms
mouse.min.js
303 ms
moment.min.js
184 ms
main.min.js
179 ms
misc-mixin.min.js
176 ms
datepicker.min.js
176 ms
jquery.cookie.min.js
183 ms
jquery.storageapi.min.js
178 ms
class.min.js
169 ms
loader.min.js
141 ms
local.min.js
129 ms
logger.min.js
130 ms
entry-factory.min.js
135 ms
console-output-handler.min.js
147 ms
formatter.min.js
138 ms
message-pool.min.js
122 ms
levels-pool.min.js
121 ms
logger-utils.min.js
104 ms
async.min.js
111 ms
registry.min.js
119 ms
js-translation.json
121 ms
modal-custom.html
118 ms
modal-popup.html
104 ms
modal-slide.html
111 ms
slider.min.js
105 ms
modal-popup.html
116 ms
calendar.min.js
105 ms
spectrum.min.js
86 ms
tinycolor.min.js
95 ms
bootstrap-datepicker.min.js
80 ms
arrays.min.js
82 ms
compare.min.js
76 ms
misc.min.js
80 ms
objects.min.js
87 ms
strings.min.js
101 ms
template.min.js
89 ms
entry.min.js
78 ms
dom-observer.min.js
69 ms
bindings.min.js
71 ms
FormData.min.js
24 ms
MutationObserver.min.js
15 ms
tooltip.html
29 ms
print.css
33 ms
southerngracefloralmarket.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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
southerngracefloralmarket.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
southerngracefloralmarket.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 Southerngracefloralmarket.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 Southerngracefloralmarket.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.
southerngracefloralmarket.com
Open Graph description is not detected on the main page of Southern Grace Floral Market. 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: