4.6 sec in total
238 ms
3.3 sec
1 sec
Welcome to marks-and-spencer.com homepage info - get ready to check Marks And Spencer best content right away, or after learning these important things about marks-and-spencer.com
Welcome to the M&S website. Shop clothing, home, furniture, beauty, food, wine, flowers & gifts. Buy now for free delivery, store collections and returns.
Visit marks-and-spencer.comWe analyzed Marks-and-spencer.com page load time and found that the first response time was 238 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
marks-and-spencer.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value17.9 s
0/100
25%
Value35.0 s
0/100
10%
Value29,160 ms
0/100
30%
Value0.159
73/100
15%
Value44.7 s
0/100
10%
238 ms
94 ms
161 ms
115 ms
27 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Marks-and-spencer.com, 11% (13 requests) were made to Tags.tiqcdn.com and 11% (13 requests) were made to Asset1.cxnmarksandspencer.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Webchat.marksandspencer.com.
Page size can be reduced by 1.4 MB (54%)
2.6 MB
1.2 MB
In fact, the total size of Marks-and-spencer.com main page is 2.6 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. Javascripts take 982.9 kB which makes up the majority of the site volume.
Potential reduce by 323.5 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 47.6 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 323.5 kB or 87% of the original size.
Potential reduce by 702 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. Marks And Spencer images are well optimized though.
Potential reduce by 656.6 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 656.6 kB or 67% of the original size.
Potential reduce by 442.0 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. Marks-and-spencer.com needs all CSS files to be minified and compressed as it can save up to 442.0 kB or 84% of the original size.
Number of requests can be reduced by 74 (67%)
111
37
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marks And Spencer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.marksandspencer.com
238 ms
mns.fear.pkg.basket.hdrftr.min.css
94 ms
mns.fear.pkg.homepage.min.css
161 ms
mns.bizglobal.min.css
115 ms
utag.sync.js
27 ms
mns.baskethead.min.js
388 ms
jquery-1.9.1.min.js
440 ms
mns.fear.pkg.custom.modernizr.min.js
440 ms
mns.fear.pkg.core.min.js
440 ms
mns.fear.pkg.newNavigation.min.js
384 ms
mns.fear.pkg.homepage.min.js
438 ms
mns.fear.pkg.pubsub.min.js
438 ms
mns.rrApiSetup.min.js
447 ms
s_code.js
448 ms
json
241 ms
utag.js
237 ms
lazyload
211 ms
493afec7f0a2152ed0b37fe110bdfe6dc590bdb0
182 ms
8b58bec65855ef58b890cb70de4c3d71553291ee
166 ms
3efeeb987c064496320b674f2141546c76c880b4
165 ms
c0ca35dc88b64c7bc1b1ca010f7bc821a8dc3e2b
164 ms
26207526b12fb3526867b01a8a1b7d07e8950c11
163 ms
18094864ac27293e55637ba408dad21053b6f234
164 ms
262a2ccf75f218ed906eaa034ee4f9bae3b2779b
175 ms
a06470acacd2f36872ae46345b2f61160574d9a4
165 ms
4e2f19c5b02a4c2e3085423f88646865a9b1ed05
164 ms
9550bfda47300a8a0eb7b7e6e799d89485402a95
173 ms
b3d4c55eb72ea85a2875307447e31ea2a08ebebb
174 ms
3b71871ed4c60b55b818d0a127af2c8dd7a63ee4
172 ms
flags_sprite.png
160 ms
global_icon_bgs.png
159 ms
sprite.png
159 ms
my-mns-logo.png
171 ms
lightbox-closer.png
161 ms
13b8be483d8b7d8ce10ce4023857ea0df934d571
165 ms
81c8ff9f51ba2432bfb70f6a924e9c3a7556faef
162 ms
7d3db24046946bc4a9a5b72aa51a3c806a97cee3
163 ms
e340cdcdd05b054bee786d1ac78ed28a3d3ef735
162 ms
1fe424ebb37398d09d4b22d5a52fc2184bdfc436
162 ms
d7365f00d21ba534f1f9d1fc84d76c1f3e3d6ea4
163 ms
82dc9ebd5d15f5ecba62d2bab09379a27eaebd51
164 ms
6cda1842e0c96e6e4fa66ce80f792e886634d353
164 ms
cat-header-line.gif
183 ms
footer_dock_sprite.png
181 ms
duck-divider.png
181 ms
multi-arrow.png
180 ms
isa-duck-bg.png
180 ms
62A9E-5MVGF-YXSN8-XJEGE-VCFNT
141 ms
general.js
1065 ms
MSGeoLocateOverLayView
196 ms
MSLondoneText-Semibold.woff
47 ms
MSLondoneText-Demibold.woff
59 ms
MandSLeedsW03Light.woff
378 ms
icomoon.woff
59 ms
icomoon.woff
62 ms
config.json
464 ms
addGeoOverlayCSS.min.js
429 ms
4b50d337a68a84706f74735db759cfe72a467a30
119 ms
MSLondoneText-Regular.woff
80 ms
utag.318.js
51 ms
utag.118.js
59 ms
utag.249.js
59 ms
utag.315.js
49 ms
utag.247.js
48 ms
utag.82.js
48 ms
utag.90.js
48 ms
utag.357.js
48 ms
utag.322.js
46 ms
utag.313.js
46 ms
4eeddffcbd725dd6ad1e99ce46c890569b2e2b98
113 ms
bat.js
150 ms
live.js
77 ms
fbevents.js
239 ms
5028;33120;3880;iframe
217 ms
conversion_async.js
64 ms
post-widget.js
40 ms
edr.js
308 ms
utag.v.js
23 ms
22339
53 ms
hit
180 ms
208 ms
generic
112 ms
adsct
476 ms
pixel.js
109 ms
s1211157703306
93 ms
multi.html
136 ms
532532436920970
54 ms
pixel
29 ms
3085
67 ms
2981
159 ms
145 ms
179 ms
s18041562268044
99 ms
366738.gif
84 ms
4538
182 ms
apid
97 ms
58 ms
tap.php
21 ms
sync
24 ms
4448
56 ms
status
53 ms
l.php
378 ms
post-widget.css
36 ms
theme-default.css
45 ms
copypaste.js
86 ms
beacon.js
153 ms
p
108 ms
shareQuote.js
19 ms
398656.gif
46 ms
p23
45 ms
15845
32 ms
pixel
33 ms
tap.php
38 ms
msarrow.png
123 ms
ucm
30 ms
ucm
36 ms
ucm
32 ms
ucm
18 ms
sd
17 ms
rmxucm
24 ms
appnexus
17 ms
marks-and-spencer.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
[role]s do not have all required [aria-*] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
marks-and-spencer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
marks-and-spencer.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
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 Marks-and-spencer.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 Marks-and-spencer.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.
marks-and-spencer.com
Open Graph description is not detected on the main page of Marks And Spencer. 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: