3 sec in total
183 ms
2.2 sec
575 ms
Click here to check amazing Mo Burberry content for Japan. Otherwise, check out these important facts you probably never knew about mo.burberry.com
Discover luxury British clothing, bags, accessories and fragrances for women and men. Free delivery available.
Visit mo.burberry.comWe analyzed Mo.burberry.com page load time and found that the first response time was 183 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
mo.burberry.com performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value13.5 s
0/100
25%
Value7.6 s
25/100
10%
Value2,530 ms
4/100
30%
Value0
100/100
15%
Value14.0 s
10/100
10%
183 ms
58 ms
39 ms
89 ms
53 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 16% of them (13 requests) were addressed to the original Mo.burberry.com, 28% (22 requests) were made to S.btstatic.com and 8% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (646 ms) relates to the external source D.la1-c1-lon.salesforceliveagent.com.
Page size can be reduced by 509.0 kB (25%)
2.1 MB
1.6 MB
In fact, the total size of Mo.burberry.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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 47.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. 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 47.6 kB or 75% of the original size.
Potential reduce by 8.3 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. Mo Burberry images are well optimized though.
Potential reduce by 452.9 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 452.9 kB or 60% of the original size.
Potential reduce by 157 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. Mo.burberry.com needs all CSS files to be minified and compressed as it can save up to 157 B or 25% of the original size.
Number of requests can be reduced by 54 (71%)
76
22
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mo Burberry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and as a result speed up the page load time.
mo.burberry.com
183 ms
mmcore.js
58 ms
cssCombined_site_18635.css
39 ms
cssCombined_landing_grid_2_18635.css
89 ms
jsCombined_min_header_18635.js
53 ms
jsCombined_min_site_18635.js
103 ms
jsCombined_min_landing_grid_2_18635.js
82 ms
tag.js
87 ms
43 ms
bg_body_v2.gif
300 ms
spinner.gif
307 ms
shared_v5.png
144 ms
spinner-small.gif
228 ms
burberryicons-regular-webfont.woff
201 ms
burberrycapitalssmall_0-webfont.woff
177 ms
perpetua-mt-w01.woff
146 ms
counter.jsp
165 ms
spinner-sprite.png
80 ms
loading-ffffff-545454.gif
122 ms
deployment.js
199 ms
tag
44 ms
MultiNoun.jsonp
171 ms
8x2_MAR_LP_HP_HERITAGE_V2
289 ms
0becd38a0e14b24d97004f9a1905449700d83ea1
165 ms
d9a86f72c8faf8cb73423a7053026581f1b64f97
164 ms
16a1c10892f50a41cb64e5724c7dca5aa324cb71.js
40 ms
e077a29f61865a729c94f22a8512f2911969ad4e.js
63 ms
ce240025c480ad2159bebd10ff10fb667e8d9956.js
35 ms
1164d48866c5139b0330e1dc026ce5623eafd151.js
26 ms
MultiNoun.jsonp
646 ms
85d3a2170d5b606044bb506739290d503ed4448c.js
3 ms
45c630d6fd96c759e4533a4689b43f695d44e0f4.js
3 ms
9fdc2e43f30098d7edb4fee98e987fff836aa90b.js
5 ms
4667f98e6c0594f4a1a88b164e9ee7f87cd9182e.js
3 ms
bf24f40335c58bab6b12de852670f87bc5c92e7a.js
33 ms
58c5ff6e0f369ad06a2a6e826b1812964f1035c7.js
3 ms
7c21a79bd924919a7c3fcae8468d06d51db4e1ed.js
4 ms
cfb2ed2783f4cac69059dd19960dd639c8b9b318.js
3 ms
9f57c595faa904a5ddb1a04f60dd1f5100f93369.js
22 ms
6e2c036524b13399ad6e555871a6c6cff9ace7c2.js
39 ms
8x2_MAR_LP_HP_HERITAGE_V2
103 ms
ca21c28fb6c902d08f82252b55d4b6b7a51284e3.js
26 ms
515dc73ee880bdcb76ec6abc86af5c32c0cf24bc.js
20 ms
b994eb307bbfd62fedb7472787f403cfaccb180a.js
30 ms
6a0b7279e4f06635d02582f57d4f3eb13bc13e72.js
3 ms
116e0af1d33fc36469160097a3500d4ce58d4a22.js
20 ms
f8aa72a28943634cb95579eee03b0d0d576eed30.js
23 ms
fc739e833c3fc4acaca33a298c7ad0db13890725.js
23 ms
atgsvcs.js
234 ms
activityi;src=4397388;type=brbrry;cat=brbrry;u1=MO;u2=;u3=;u4=;u5=;num=8418912090;ord=1;prd=
187 ms
activityi;src=4397388;type=brbrry;cat=home;u1=MO;num=8418912090;ord=1;prd=
172 ms
p13n.js
96 ms
fbds.js
317 ms
activityi;src=4397388;type=brbrry;cat=brbrry-s;u1=MO;u2=;u3=;u4=;u5=;ord=2304240616504.103;prd=
209 ms
fbevents.js
371 ms
x30975r82104042
367 ms
tag
70 ms
analytics.js
233 ms
2fedcc0f-e74e-4d94-9044-f4e4ccf6f6ec
249 ms
dc.js
284 ms
conversion.js
295 ms
294 ms
beacon
354 ms
conversion_async.js
293 ms
L21rdC80MTAvcGlkLzM3MzA1NDE3L3QvMA
321 ms
xd.js
271 ms
lr.php
509 ms
209 ms
linkid.js
38 ms
ec.js
108 ms
174 ms
99 ms
98 ms
collect
23 ms
collect
51 ms
collect
19 ms
collect
46 ms
46 ms
38 ms
mo.burberry.com accessibility score
mo.burberry.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mo.burberry.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 Mo.burberry.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 Mo.burberry.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.
mo.burberry.com
Open Graph description is not detected on the main page of Mo Burberry. 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: