3.8 sec in total
798 ms
2.3 sec
691 ms
Visit metro.digital now to see the best up-to-date METRO content and also check out these interesting facts you probably never knew about metro.digital
As a product-driven organization, we develop digital solutions for the METRO global wholesale business.
Visit metro.digitalWe analyzed Metro.digital page load time and found that the first response time was 798 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
metro.digital performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value5.8 s
15/100
25%
Value4.8 s
67/100
10%
Value200 ms
89/100
30%
Value0.031
100/100
15%
Value6.4 s
60/100
10%
798 ms
56 ms
77 ms
43 ms
107 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Metro.digital, 2% (1 request) were made to Siteimproveanalytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (843 ms) belongs to the original domain Metro.digital.
Page size can be reduced by 523.4 kB (15%)
3.5 MB
3.0 MB
In fact, the total size of Metro.digital 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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 92.7 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 22.4 kB, which is 21% 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 92.7 kB or 85% of the original size.
Potential reduce by 55.4 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. METRO images are well optimized though.
Potential reduce by 186.8 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 186.8 kB or 55% of the original size.
Potential reduce by 188.5 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. Metro.digital needs all CSS files to be minified and compressed as it can save up to 188.5 kB or 84% of the original size.
Number of requests can be reduced by 21 (48%)
44
23
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of METRO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
metro.digital
798 ms
optimized-min.css
56 ms
optimized-min.css
77 ms
optimized-min.css
43 ms
siteimprove.js
107 ms
optimized-min.js
198 ms
optimized-min.js
111 ms
optimized-min.js
111 ms
optimized-min.js
298 ms
bootstrap-select1139.js
350 ms
siteanalyze_1634.js
54 ms
gtm.js
75 ms
mdlogo.svg
38 ms
hero12x_compressed.png
193 ms
hero22x.png
194 ms
hero32x_compressed.png
193 ms
hero42x-compressed.png
209 ms
heroillustration2x.png
304 ms
engineering-icon.png
303 ms
right_arrow_dark.svg
208 ms
engineering-hub-teaser.png
386 ms
design-icon.png
368 ms
design-hub-teaser.png
303 ms
product-icon.png
471 ms
product-hub-teaser.png
448 ms
data-icon.png
380 ms
data-hub-teaser.png
393 ms
cloudcomputinghub.png
565 ms
img_join.png
412 ms
right_arrow.svg
404 ms
1imgecommthumb2x.png
537 ms
2imgmobileassistantthumb2x.png
495 ms
3imgcrmthumb2x.png
544 ms
4imgdigitalinvoicingthumb2x.png
773 ms
5imgcreditmanagementthumb2x.png
603 ms
7imgdeliveryfulfillmentthumb2x.png
775 ms
6imgfleetmanagementthumb2x.png
704 ms
checkoutproductsthumb2x.png
696 ms
locations.svg
647 ms
products.svg
634 ms
employees.svg
658 ms
Gotham-Regular.otf
670 ms
metro_logo.svg
700 ms
germany.svg
843 ms
romania.svg
730 ms
vietnam.svg
708 ms
Gotham-Bold.otf
599 ms
metroicons_woff.woff
618 ms
Socicon_ttf.ttf
728 ms
fontawesome-webfont-woff.woff
643 ms
metro.digital accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
metro.digital best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
metro.digital 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metro.digital can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Metro.digital 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.
metro.digital
Open Graph data is detected on the main page of METRO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: