5.2 sec in total
159 ms
3.3 sec
1.8 sec
Welcome to davidaustin.com homepage info - get ready to check David Austin best content for United States right away, or after learning these important things about davidaustin.com
For the finest cut roses, it has to be David Austin. Effortlessly elegant and breathtakingly beautiful, there is no better rose for your wedding.
Visit davidaustin.comWe analyzed Davidaustin.com page load time and found that the first response time was 159 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
davidaustin.com performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value11.0 s
0/100
25%
Value12.0 s
4/100
10%
Value1,480 ms
14/100
30%
Value0.003
100/100
15%
Value13.6 s
11/100
10%
159 ms
69 ms
42 ms
117 ms
32 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 71% of them (67 requests) were addressed to the original Davidaustin.com, 11% (10 requests) were made to Mlri412iwjbc.i.optimole.com and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Mlri412iwjbc.i.optimole.com.
Page size can be reduced by 181.3 kB (9%)
2.1 MB
1.9 MB
In fact, the total size of Davidaustin.com main page is 2.1 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 114.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. 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 114.7 kB or 78% of the original size.
Potential reduce by 245 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. David Austin images are well optimized though.
Potential reduce by 36.4 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 36.4 kB or 11% of the original size.
Potential reduce by 29.9 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. Davidaustin.com needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 16% of the original size.
Number of requests can be reduced by 60 (76%)
79
19
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of David Austin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
davidaustin.com
159 ms
www.davidaustin.com
69 ms
uc.js
42 ms
yai8sxt.css
117 ms
sbi-styles.min.css
32 ms
frontend.css
49 ms
init.css
41 ms
cleantalk-public.min.css
55 ms
bootstrap.min.css
39 ms
client.css
52 ms
callout.css
52 ms
style.min.css
67 ms
theme.min.css
62 ms
header-footer.min.css
68 ms
dflip.min.css
58 ms
elementor-icons.min.css
65 ms
frontend.min.css
74 ms
swiper.min.css
81 ms
post-4889.css
95 ms
frontend.min.css
84 ms
jet-tabs-frontend.css
96 ms
global.css
97 ms
post-7.css
100 ms
post-8472.css
99 ms
post-5273.css
102 ms
post-17218.css
104 ms
css
52 ms
fontawesome.min.css
107 ms
solid.min.css
110 ms
brands.min.css
111 ms
jquery.min.js
115 ms
jquery-migrate.min.js
119 ms
apbct-public-bundle.min.js
134 ms
popper.min.js
125 ms
bootstrap.min.js
129 ms
front.js
123 ms
6423.js
49 ms
js
93 ms
js
118 ms
animations.min.css
136 ms
wp-polyfill-inert.min.js
133 ms
regenerator-runtime.min.js
265 ms
wp-polyfill.min.js
266 ms
hooks.min.js
270 ms
i18n.min.js
246 ms
jquery.form.min.js
236 ms
dynamic-conditions-public.js
237 ms
jpibfi.client.js
225 ms
dflip.min.js
226 ms
jquery.sticky.min.js
227 ms
jquery.smartmenus.min.js
226 ms
imagesloaded.min.js
285 ms
sbi-scripts.min.js
284 ms
dwf.js
279 ms
webpack-pro.runtime.min.js
278 ms
webpack.runtime.min.js
277 ms
frontend-modules.min.js
264 ms
frontend.min.js
265 ms
waypoints.min.js
305 ms
core.min.js
304 ms
frontend.min.js
301 ms
elements-handlers.min.js
247 ms
jet-tabs-frontend.min.js
246 ms
p.css
31 ms
fbevents.js
171 ms
david-austin-rose-arch.jpg
1396 ms
david-austin-wedding-roses.jpg
1582 ms
david-austin-wedding-roses-urn-arrangement.jpg
2880 ms
bride-holding-wedding-bouquet-david-austin-roses.jpg
1384 ms
florist-designing-wedding-arrangements.webp
1384 ms
wedding-arbour-floral-design.jpg
1383 ms
pink-wedding-roses.jpg
1385 ms
outdoor-wedding-reception-bride.jpg
1389 ms
perfect-sunshine-bridal-bouquet-recipe-scaled.jpg
1395 ms
placeholder.png
1389 ms
sbi-sprite.png
199 ms
david-austin-roses-logo-midnight.webp
199 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-6_RkBI95.woff
203 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-2fRkBI95.woff
216 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-NfNkBI95.woff
217 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-DPNkBI95.woff
219 ms
SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPuGi-a_NkBI95.woff
217 ms
fa-solid-900.woff
127 ms
whitegarden-regular-webfont.woff
127 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7e8QL99U64.woff
129 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7eOQL99U64.woff
128 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7diR799U64.woff
130 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7dbR799U64.woff
131 ms
SlGFmQSNjdsmc35JDF1K5GRwUjcdlttVFm-rI7c8R799U64.woff
131 ms
fa-brands-400.woff
126 ms
448740286_1135993957613216_185284300078845788_nfull.jpg
293 ms
448724798_314374658295759_4584655632063994839_nfull.jpg
55 ms
448474730_423452850692141_8971635885149867327_nfull.jpg
54 ms
448224206_1840028349808723_6204012511714225312_nfull.jpg
55 ms
448131248_808272734613049_6618956814851111473_nfull.jpg
95 ms
davidaustin.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
davidaustin.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
davidaustin.com SEO score
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 Davidaustin.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 Davidaustin.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.
davidaustin.com
Open Graph data is detected on the main page of David Austin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: