3.6 sec in total
201 ms
3.1 sec
291 ms
Visit allsaints.com now to see the best up-to-date ALLSAINTS content for United States and also check out these interesting facts you probably never knew about allsaints.com
Shop the ALLSAINTS 2024 collection of leather jackets, clothing & accessories for men & women. Free UK delivery & returns.
Visit allsaints.comWe analyzed Allsaints.com page load time and found that the first response time was 201 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.
allsaints.com performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value12.7 s
0/100
25%
Value21.6 s
0/100
10%
Value17,800 ms
0/100
30%
Value0.348
32/100
15%
Value31.0 s
0/100
10%
201 ms
115 ms
88 ms
142 ms
155 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 19% of them (32 requests) were addressed to the original Allsaints.com, 14% (23 requests) were made to Images.allsaints.com and 13% (22 requests) were made to Eu-sonar.sociomantic.com. The less responsive or slowest element that took the longest time to load (629 ms) belongs to the original domain Allsaints.com.
Page size can be reduced by 1.7 MB (49%)
3.5 MB
1.8 MB
In fact, the total size of Allsaints.com main page is 3.5 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. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 159.6 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 34.2 kB, which is 18% 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 159.6 kB or 83% of the original size.
Potential reduce by 31.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. ALLSAINTS images are well optimized though.
Potential reduce by 1.3 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.3 MB or 67% of the original size.
Potential reduce by 224.2 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. Allsaints.com needs all CSS files to be minified and compressed as it can save up to 224.2 kB or 84% of the original size.
Number of requests can be reduced by 111 (73%)
153
42
The browser has sent 153 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ALLSAINTS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
allsaints.com
201 ms
www.allsaints.com
115 ms
tag_container.js
88 ms
underscore.min.js
142 ms
jquery-1.7.2.min.js
155 ms
jquery.cookie.js
219 ms
jquery.pubsub.js
146 ms
hammer.min.js
172 ms
jquery.royalslider.min.js
234 ms
jquery.placeholder.min.js
287 ms
isInViewport.min.js
282 ms
spin.min.js
339 ms
select2.min.js
331 ms
AS_bundle.js
356 ms
grid.js
382 ms
userState.js
493 ms
jquery.blockUI.js
433 ms
index.css
629 ms
js
91 ms
Widgets.js
418 ms
slick.css
24 ms
slick.min.js
6 ms
conversion.js
35 ms
ga.js
15 ms
login1.js
534 ms
__utm.gif
24 ms
collect
68 ms
Amazon_Welcome_WW.jpg
26 ms
Amazon_Welcome_MW.jpg
21 ms
2016-05-01-UK-new-arrivals-womens.jpg
22 ms
2016-05-01-UK-new-arrivals-mens.jpg
19 ms
2016-18-02-UK-capital-collection-february-lookbook-WW-mobile.jpg
23 ms
2016-11-02-UK-capital-collection-pearl-hobo-mobile.jpg
18 ms
2016-11-02-UK-capital-collection-pearl-hobo.jpg
24 ms
2016-18-02-UK-capital-collection-february-lookbook-WW.jpg
24 ms
2016-18-02-UK-leather-womens.jpg
27 ms
2016-18-02-UK-shirts-mens.jpg
27 ms
2016-05-01-UK-film-the-spring-2016-collection-island-life.jpg
23 ms
307 ms
FuturaW01Light.woff
167 ms
Ramskull.ttf
209 ms
Ramskull.eot
198 ms
FuturaW01Book.woff
268 ms
blank.gif
166 ms
261 ms
425 ms
124 ms
Amazon_Welcome_WW.jpg
83 ms
567 ms
342 ms
widgets
178 ms
donations.css
110 ms
Amazon_Welcome_MW.jpg
36 ms
2016-05-01-UK-new-arrivals-womens.jpg
36 ms
2016-05-01-UK-new-arrivals-mens.jpg
35 ms
2016-18-02-UK-capital-collection-february-lookbook-WW-mobile.jpg
34 ms
2016-11-02-UK-capital-collection-pearl-hobo-mobile.jpg
34 ms
2016-18-02-UK-leather-womens.jpg
35 ms
2016-18-02-UK-shirts-mens.jpg
36 ms
2016-05-01-UK-film-the-spring-2016-collection-island-life.jpg
47 ms
2016-05-01-UK-film-the-spring-2016-collection-island-life.jpg
36 ms
46 ms
forester-client-978607279._V369474569_.js
149 ms
jserrors-1871966242._V375149217_.js
164 ms
spa-widget._V301812537_.css
164 ms
spa-library._V297680853_.js
174 ms
new-CommonWidgetLib._V297600410_.js
168 ms
spa-widget._V297600412_.js
167 ms
jquery-1.7.2.min.js
195 ms
tag_container.js
171 ms
TimesLTW01Roman.woff
167 ms
opentag-56375-272322.js
35 ms
gtm.js
37 ms
qtracker-v3-min.js
45 ms
smartserve-2287.js
173 ms
ip
253 ms
collect.js
39 ms
opentag-56375-1528133.js
38 ms
ri.min.js
627 ms
analytics.js
15 ms
fbds.js
136 ms
prum.min.js
10 ms
3708.js
300 ms
allsaints-uk
232 ms
activityi;src=4302373;type=count639;cat=allsa409;u6=GB;ord=2153552421741;~oref=http%3A%2F%2Fwww.allsaints.com%2F
77 ms
activityi;src=4394959;type=ukmai301;cat=ukhom672;ord=3946946612629;~oref=http%3A%2F%2Fwww.allsaints.com%2F
79 ms
t2
203 ms
t2
279 ms
collect
7 ms
collect
34 ms
emptyBasket.html
122 ms
102 ms
track_page_view
38 ms
1456749897809.716725
209 ms
visitor-history.4.js
17 ms
Amazon_Welcome_WW.jpg
10 ms
Amazon_Welcome_MW.jpg
13 ms
view
101 ms
view
202 ms
1456749897809.716725
142 ms
LwA.png
13 ms
widgets
177 ms
UserMatch.ashx
35 ms
sync.cgi
271 ms
rum
76 ms
u.php
38 ms
serve
29 ms
30 ms
pixel
71 ms
usersync
41 ms
match
29 ms
Pug
69 ms
91 ms
info.php
207 ms
tg-03.yieldpartners.com
314 ms
merge
6 ms
44 ms
sd
38 ms
ad
99 ms
tap.php
34 ms
match
117 ms
match
389 ms
rum
44 ms
match
102 ms
match
189 ms
UserMatch.ashx
26 ms
u.php
47 ms
merge
15 ms
serve
24 ms
27 ms
pixel
27 ms
usersync
24 ms
match
24 ms
sd
23 ms
Pug
29 ms
tap.php
23 ms
tg-03.yieldpartners.com
230 ms
info.php
171 ms
sync.cgi
267 ms
rum
35 ms
40 ms
match
164 ms
match
154 ms
match
146 ms
20 ms
match
405 ms
match
176 ms
nr-768.min.js
84 ms
cm.gif
65 ms
match
153 ms
match
155 ms
match
152 ms
mapuser
103 ms
cm.gif
26 ms
match
139 ms
match
126 ms
63f3062c7d
128 ms
match
279 ms
rInteract-2.0.3.min.js
234 ms
mapuser
102 ms
match
102 ms
match
116 ms
match
142 ms
match
101 ms
nr-768.min.js
19 ms
5 ms
63f3062c7d
51 ms
beacon.gif
82 ms
handshake.js
62 ms
allsaints.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
[role]s are not contained by their required parent element
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
allsaints.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
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
allsaints.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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Allsaints.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 Allsaints.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.
allsaints.com
Open Graph description is not detected on the main page of ALLSAINTS. 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: