7.1 sec in total
1.3 sec
5.4 sec
393 ms
Welcome to askdrake.com homepage info - get ready to check Askdrake best content right away, or after learning these important things about askdrake.com
We supply & build pub furniture for pubs, bars, clubs, cafes, restaurants, hotels & coffee shops throughout the UK. In business for over 50yrs.
Visit askdrake.comWe analyzed Askdrake.com page load time and found that the first response time was 1.3 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
askdrake.com performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value12.5 s
0/100
25%
Value30.3 s
0/100
10%
Value34,200 ms
0/100
30%
Value0.159
73/100
15%
Value46.8 s
0/100
10%
1298 ms
110 ms
299 ms
273 ms
603 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 66% of them (72 requests) were addressed to the original Askdrake.com, 13% (14 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Askdrake.com.
Page size can be reduced by 132.0 kB (12%)
1.1 MB
935.4 kB
In fact, the total size of Askdrake.com main page is 1.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. 80% 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 576.1 kB which makes up the majority of the site volume.
Potential reduce by 105.0 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 105.0 kB or 83% of the original size.
Potential reduce by 25.0 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. Askdrake images are well optimized though.
Potential reduce by 1.0 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 884 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. Askdrake.com has all CSS files already compressed.
Number of requests can be reduced by 67 (71%)
95
28
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Askdrake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.askdrake.com
1298 ms
wp-emoji-release.min.js
110 ms
6bkmm.css
299 ms
6bkmm.css
273 ms
6bkmm.css
603 ms
6bkmm.css
368 ms
css
115 ms
6bkmm.css
264 ms
6bqi6.css
394 ms
6bkmm.js
515 ms
6bkmm.js
342 ms
6bkmm.js
405 ms
js
134 ms
font-awesome.min.css
126 ms
sdk.js
106 ms
wp-polyfill.min.js
585 ms
index.js
449 ms
js.cookie.min.js
450 ms
woocommerce.min.js
457 ms
cart-fragments.min.js
536 ms
frontend.min.js
537 ms
skip-link-focus-fix.min.js
546 ms
tether.min.js
895 ms
bootstrap.min.js
897 ms
slick.min.js
895 ms
jquery.waypoints.min.js
896 ms
waypoints-sticky.min.js
897 ms
pace.min.js
897 ms
typeahead.bundle.min.js
913 ms
handlebars.min.js
915 ms
jquery.easing.min.js
914 ms
scrollup.min.js
914 ms
scripts.min.js
915 ms
jquery-actual.min.js
916 ms
imagesloaded.min.js
893 ms
underscore.min.js
894 ms
verge.min.js
895 ms
hooks.min.js
895 ms
i18n.min.js
895 ms
jquery-strongslider.min.js
896 ms
api.js
136 ms
controller.min.js
895 ms
index.js
841 ms
smush-lazy-load.min.js
680 ms
kingcomposer.min.js
678 ms
masonry.min.js
603 ms
jquery.prettyPhoto.min.js
635 ms
wp-embed.min.js
585 ms
header-bg.jpg
1179 ms
analytics.js
198 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFWUUz.woff
248 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFWUUz.woff
385 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFWUUz.woff
386 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-ro-FWUUz.woff
368 ms
techmarket-icons.woff
161 ms
fontawesome-webfont.woff
161 ms
sdk.js
209 ms
wp-polyfill-fetch.min.js
254 ms
wp-polyfill-dom-rect.min.js
252 ms
wp-polyfill-url.min.js
254 ms
wp-polyfill-formdata.min.js
252 ms
wp-polyfill-element-closest.min.js
251 ms
wp-polyfill-object-fit.min.js
413 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8tdE3U5f4Q.woff
234 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8tvE3U5f4Q.woff
235 ms
iJWbBXyIfDnIV7nEt3KSJbVDV49rz8v0FHU5f4Q.woff
235 ms
collect
148 ms
collect
616 ms
recaptcha__en.js
430 ms
barfurniture.png
342 ms
banners-02.png
342 ms
banners-03.png
342 ms
banners-04.png
341 ms
banners-bespoke.jpg
482 ms
banner-recentwork.jpg
341 ms
banner-needaquoteortalk.png
710 ms
ajax-loader.gif
109 ms
ga-audiences
36 ms
page.php
143 ms
fa-solid-900.woff
337 ms
fa-solid-900.woff
552 ms
fa-regular-400.woff
336 ms
fa-regular-400.woff
374 ms
banners.png
333 ms
pexels-photo-4-233x350.jpg
433 ms
bars-233x350.jpg
427 ms
KMWcFVqNByY.css
51 ms
KCBgpVwfLM_.css
59 ms
nYa8oQZnpdr.js
66 ms
iiDbYMCPtB3.js
61 ms
WOLN5pzG8JN.js
61 ms
q6VzhXzzuec.js
63 ms
irCgPB7CJbM.js
61 ms
I-9YqvQlahI.js
62 ms
SixM03AXEw8.js
111 ms
YJojGYumZIr.js
111 ms
1lYRIUv3fB9.js
110 ms
bar33-233x350.jpg
363 ms
IMG-20190830-WA0025-233x350.jpg
364 ms
pexels-photo-225236-233x350.jpeg
379 ms
t42-233x350.jpg
440 ms
houston-veneer-rfu-seat-sidechair-233x350.jpg
441 ms
305844549_466949135448316_6010209695884050694_n.jpg
136 ms
01wobW0ovxv.js
99 ms
305581756_466949138781649_8686927034397962512_n.png
195 ms
UXtr_j2Fwe-.png
99 ms
99 ms
xgVgalBG80z.png
18 ms
bs40-233x350.jpg
90 ms
askdrake.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 input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
[aria-*] attributes do not have valid values
ARIA IDs 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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
askdrake.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
askdrake.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Askdrake.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 Askdrake.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.
askdrake.com
Open Graph data is detected on the main page of Askdrake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: