5.7 sec in total
265 ms
4.6 sec
804 ms
Visit oliversweeney.com now to see the best up-to-date Oliver Sweeney content for United Kingdom and also check out these interesting facts you probably never knew about oliversweeney.com
Discover our men's handcrafted shoes, boots and clothing range. We design and produce high quality products from exceptional materials and established ethical sources Free UK delivery on orders ov...
Visit oliversweeney.comWe analyzed Oliversweeney.com page load time and found that the first response time was 265 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
oliversweeney.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value8.8 s
1/100
25%
Value13.6 s
2/100
10%
Value5,720 ms
0/100
30%
Value0.019
100/100
15%
Value22.6 s
1/100
10%
265 ms
721 ms
181 ms
269 ms
269 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 37% of them (53 requests) were addressed to the original Oliversweeney.com, 13% (19 requests) were made to Media.oliversweeney.com and 3% (4 requests) were made to Pixel-geo.prfct.co. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Media.oliversweeney.com.
Page size can be reduced by 2.6 MB (33%)
8.1 MB
5.4 MB
In fact, the total size of Oliversweeney.com main page is 8.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. 75% 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 5.6 MB which makes up the majority of the site volume.
Potential reduce by 101.2 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 27.0 kB, which is 22% 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 101.2 kB or 83% of the original size.
Potential reduce by 837.2 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, Oliver Sweeney needs image optimization as it can save up to 837.2 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.4 MB
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 1.4 MB or 71% of the original size.
Potential reduce by 265.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. Oliversweeney.com needs all CSS files to be minified and compressed as it can save up to 265.9 kB or 83% of the original size.
Number of requests can be reduced by 99 (72%)
137
38
The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oliver Sweeney. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
oliversweeney.com
265 ms
www.oliversweeney.com
721 ms
bootstrap.min.css
181 ms
jquery.nouislider.min.css
269 ms
slick.css
269 ms
slick-theme.css
282 ms
main.css
283 ms
bootstrap-override.css
284 ms
modules.css
285 ms
html-semantic.css
355 ms
html-agency.css
357 ms
settings.css
369 ms
settings-ie8.css
375 ms
jquery.sidr.dark.css
376 ms
jquery-ui.css
378 ms
popup-manager.css
438 ms
font-awesome.min.css
43 ms
css
78 ms
2900151597.js
261 ms
iframe_api
99 ms
jquery.min.js
537 ms
global.js
504 ms
carousel.js
502 ms
heightShim.js
503 ms
home.js
503 ms
category.js
534 ms
bootstrap.min.js
551 ms
jquery.nouislider.all.min.js
554 ms
placeholders.min.js
550 ms
imagesloaded.pkgd.js
554 ms
imagesloaded.js
608 ms
slick.js
671 ms
imgOptimiser.js
715 ms
jquery.elevatezoom.min.js
715 ms
dashboard.js
717 ms
plugins.js
714 ms
jquery-ui-dialog.min.js
800 ms
popup-manager.js
984 ms
jquery.themepunch.plugins.min.js
997 ms
jquery.themepunch.revolution.min.js
1010 ms
scroll-to-fixed.js
984 ms
jquery.sidr.min.js
983 ms
jquery.autocomplete.min.js
845 ms
48167_a42e1c29515bd27.jpg
1483 ms
sweeneylogo.png
709 ms
pound_s.png
678 ms
dollar_s.png
679 ms
euro_s.png
759 ms
gold-trusted-merchant.jpg
893 ms
facebook.jpg
758 ms
instagram.jpg
878 ms
twitter.jpg
879 ms
youtube.jpg
879 ms
animatedgif.gif
892 ms
47425_30102aa3a9a2ce1.jpg
1992 ms
47416_d6cebf7721eef85.jpg
1960 ms
48500_9a3c4e76328dc50.jpg
1887 ms
48501_4dabf54de64d975.jpg
1299 ms
48498_e80ce37978afec3.jpg
1889 ms
47422_27d210de03fb9f8.jpg
1474 ms
48499_44e7c7e3cd71e7c.jpg
1891 ms
47823_d1fe6ed8ec7bd88.jpg
1892 ms
45102800_b703e7c801fa4ec.jpg
1889 ms
39975800_ee644084e9e4c6a.jpg
1889 ms
41925800_3e9f0b25bd08485.jpg
1954 ms
43837800_ccf1a99288f7046.jpg
1892 ms
45008_986382a7562604d.jpg
2177 ms
48358_523fd112890014b.jpg
2004 ms
41931_2211c82cd98de3d.jpg
2007 ms
41932_2010ce5b94323fe.jpg
2113 ms
41935_a6f07a239f3d71c.jpg
2046 ms
42176_f360ace553d3c0c.jpg
2153 ms
33535gillsansmt.woff
1081 ms
gtm.js
96 ms
social-sprite.png
972 ms
www-widgetapi.js
135 ms
fontawesome-webfont.woff
9 ms
analytics.js
178 ms
js
177 ms
conversion_async.js
176 ms
fo.js
192 ms
tag.js
515 ms
oct.js
514 ms
fbevents.js
152 ms
550fe7e154acb5868200005e.js
158 ms
code.js
778 ms
B9253856.125697139;sz=1x2;ord=1550226960
187 ms
111831.ct.js
552 ms
activityi;src=5180226;type=vists;cat=visit0;ord=2240281212702;~oref=https%3A%2F%2Fwww.oliversweeney.com%2F
165 ms
widget_v2.132.js
98 ms
430 ms
gtmp_compiled_wPC6t3gu0Jc.js
410 ms
ec.js
208 ms
574 ms
collect
181 ms
channels.js
398 ms
loader.gif
359 ms
timer.png
359 ms
capture-apps-4.5.0.js
139 ms
adsct
303 ms
adsct
302 ms
lidar.js
137 ms
lqs.aspx
346 ms
tagjs
23 ms
223 ms
216 ms
215 ms
iframeStorage.html
237 ms
Pug
137 ms
adsct
111 ms
ga-audiences
108 ms
pixel
138 ms
yieldify_1449674132.js
138 ms
56309582e4b07ce01f05a945.json
239 ms
assist.js
121 ms
cb
79 ms
cb
6 ms
ncm
23 ms
tap.php
41 ms
iframeStorage.js
78 ms
sd
43 ms
skimtag.oliversweeney.com.js
11 ms
lio.js
175 ms
66 ms
68 ms
cb
6 ms
skimtag
68 ms
io.js
65 ms
undefined
43 ms
appsmanagerinit
587 ms
26 ms
default
38 ms
ecbb7b8d89958de395d24ea9338757c6
60 ms
avatar_simple_visitor.png
121 ms
aL63HcygAAVYuCCsAAA==
4 ms
inspectlet.js
56 ms
ld.js
150 ms
nr-632.min.js
133 ms
292345339
103 ms
b42b2afd60
124 ms
event
55 ms
event
350 ms
campaigns.json
130 ms
dis.aspx
387 ms
oliversweeney.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
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.
oliversweeney.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
Page has valid source maps
oliversweeney.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Oliversweeney.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 Oliversweeney.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.
oliversweeney.com
Open Graph description is not detected on the main page of Oliver Sweeney. 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: