4.6 sec in total
456 ms
3.8 sec
390 ms
Visit mobile.walmart.com now to see the best up-to-date Mobile Walmart content for United States and also check out these interesting facts you probably never knew about mobile.walmart.com
Shop Walmart.com for Every Day Low Prices. Free Shipping on Orders $35+ or Pickup In-Store and get a Pickup Discount. Open a Walmart Credit Card to Save Even More!
Visit mobile.walmart.comWe analyzed Mobile.walmart.com page load time and found that the first response time was 456 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mobile.walmart.com performance score
456 ms
26 ms
25 ms
25 ms
38 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mobile.walmart.com, 13% (15 requests) were made to Beacon.walmart.com and 4% (5 requests) were made to V4.moatads.com. The less responsive or slowest element that took the longest time to load (799 ms) relates to the external source I5.walmartimages.com.
Page size can be reduced by 3.1 MB (61%)
5.0 MB
2.0 MB
In fact, the total size of Mobile.walmart.com main page is 5.0 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. 85% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 511.1 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 511.1 kB or 85% of the original size.
Potential reduce by 61.0 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. Mobile Walmart images are well optimized though.
Potential reduce by 1.7 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.7 MB or 72% of the original size.
Potential reduce by 810.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. Mobile.walmart.com needs all CSS files to be minified and compressed as it can save up to 810.9 kB or 84% of the original size.
Number of requests can be reduced by 61 (60%)
101
40
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Walmart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.walmart.com
456 ms
k2-_e1c86c61-fbe6-4e66-bf40-c7be612ba40d.v1.css
26 ms
k2-_5423d425-f9e8-4480-867d-ad430e1f436d.v1.css
25 ms
k2-_b8b17a23-2698-4bb3-8b3f-eee5d747d46d.v1.css
25 ms
beacon.js
38 ms
gpt.js
25 ms
k2-_ce6b2cd5-7246-488c-9811-0f03b44ffd05.v572.js
27 ms
coreSpaJq.1.11.3.min.10003.js
84 ms
capabilities.min.js
29 ms
k2-_1cf91030-5b66-42d4-88af-42da1d47cf61.v501.js
20 ms
ads.js
45 ms
k2-_c9ccdca0-c15a-4fe0-944e-87bc2fcf45a3.v1.js
29 ms
k2-_e3db6f3f-bb49-4b26-ad59-3ab8987390ea.v27.js
20 ms
ss-trackingScript.min.57172.js
114 ms
cdn-test.min.js
23 ms
fqp0lia.js
188 ms
k2-_c26840ed-0ac3-478d-9173-398eaa1faef2.v11.png
167 ms
k2-_2a2a00c5-edc9-4524-9feb-bd1bcb0703b2.v1.jpg-abd8d24aa74928c614d7ecc1de82dc7c691e12c5-optim-144x144.jpg
151 ms
k2-_ce7acc02-472e-431f-ad50-d33493b7b8a4.v1.jpg
69 ms
k2-_2c8177ab-6bad-4ee4-841f-5d57ac4ca364.v1.jpg
52 ms
k2-_b36c683c-08c9-43af-bc54-9480df7cd8eb.v1.jpg
52 ms
k2-_abd80366-7ade-49e5-850b-f2029d4f54ee.v1.jpg
59 ms
k2-_bb3e8923-697c-476f-a3e7-6cfc90587a42.v1.jpg
53 ms
k2-_058b425d-18db-4ee7-bb57-2fd8ecd55918.v2.jpg
54 ms
k2-_b950a29f-ecde-4837-9fa2-b5a6f51253c4.v1.jpg
54 ms
k2-_681506f0-7103-45e7-be0d-9566ef83298b.v1.jpg
58 ms
k2-_50663c86-5436-487e-a67a-b11a3156ebb8.v1.png
55 ms
k2-_f71a9e3f-e019-4035-baa0-02e1d0e4854d.v2.jpg
58 ms
k2-_432da6c6-18d8-44c9-a694-22f9d31f1cf4.v1.jpg
59 ms
k2-_af5aad16-07a9-4595-9a71-8943bfa1ee87.v2.jpg
60 ms
k2-_604b1695-89a4-496c-8e53-d16b64f7b797.v1.jpg
60 ms
k2-_ad5d684f-8be8-4f15-a23c-10cae3008f75.v1.jpg
67 ms
k2-_92cef780-b663-49aa-bcfd-1401bc2ca051.v2.jpg
63 ms
k2-_9b7c5dbe-d972-4871-93f9-eabfec7fb64a.v1.jpg
63 ms
k2-_37c623f0-9787-455e-b50a-6acc2a9ef216.v1.jpg
62 ms
k2-_013aa511-101b-4bce-884d-5d9a097941ce.v1.jpg
66 ms
k2-_88635123-2ec8-489d-a90e-3d66cf541593.v1.jpg
69 ms
k2-_59f86b6a-54ed-4158-a957-f3185fd23c33.v1.jpg
69 ms
k2-_d2e4a8bb-8426-4daa-8ea8-f71a1d998676.v1.jpg
71 ms
k2-_2619b3f3-7dfe-49e8-8113-b23f5fcb3604.v1.jpg
70 ms
k2-_3eed9b6f-079e-4015-a832-5fb4723e5173.v1.jpg
72 ms
k2-_00107004-c887-4ff5-baad-4881a0c4c0cf.v1.jpg
71 ms
k2-_b8c372b4-04ee-4579-9508-927625d49f71.v1.jpg
73 ms
k2-_014d52b0-02bc-4510-a8d1-4b5183255d40.v1.jpg
73 ms
k2-_0a91c16a-1b70-438e-b5ca-afda16f16689.v1.jpg
74 ms
k2-_a1b91911-e21d-494c-bc8a-39586855d5f7.v1.jpg
75 ms
k2-_3900a674-673c-4304-bc02-b48a83bd009e.v1.jpg
76 ms
pubads_impl_82.js
70 ms
k2-_f9ec9304-9279-4607-8c81-f0c654196a74.v1.js
74 ms
k2-_1890fb76-ddec-483d-9807-72e77096a038.v1.woff
72 ms
fqp0lia-d.css
254 ms
container.html
238 ms
k2-_2b912b3a-9420-4168-b657-7abb9f99260c.v1.css
220 ms
ads
272 ms
beacon
112 ms
k2-_555f7d2c-00ab-41ec-a0bb-99dd106eeb8c.v1.js
27 ms
rum.js;D_S63i-jV5JEIAwtlxFKhR3mrk4
116 ms
k2-_4f33f46d-422f-42a2-ba81-67b0d9d8f611.v1.js
20 ms
k2-_54bc4ec4-ade2-4bae-95ed-bdd784d167a0.v11.js
112 ms
k2-_c8be6ccc-613d-4920-87b2-1ed926e8423a.v11.js
21 ms
k2-_04a32edc-83d9-4c36-83ba-32d6f69c78f3.v11.js
20 ms
M8j4BUtBWAYAAAA=
17 ms
0P2jz8zyPgFS0FYBgAAAA==
17 ms
0P2jz8zyPgFS0FYBgAAAA==
17 ms
imgad
354 ms
visit.jpg
462 ms
moatad.js
363 ms
latest.js
356 ms
osd.js
305 ms
k2-_0167ae70-64d5-475b-b3de-cfa050d5e638.v1.js
247 ms
rum.gif
292 ms
beacon.gif
247 ms
rum.gif
248 ms
rum.gif
254 ms
beacon.gif
250 ms
rum.gif
253 ms
beacon.gif
254 ms
rum.gif
292 ms
beacon.gif
290 ms
p.gif
234 ms
k2-_0fbd9803-dba3-401e-bf7d-3832e960acb9.v11.js
31 ms
main.js
58 ms
pixel.gif
38 ms
pixel.gif
45 ms
pixel.gif
9 ms
latest.js
3 ms
brandlift.php
200 ms
mt.gif
9 ms
mt.gif
8 ms
k2-_e27e0a8f-7541-48f3-9d09-36179066c915.v1.jpg
799 ms
rum.gif
461 ms
k2-_e1c86c61-fbe6-4e66-bf40-c7be612ba40d.v1.css
335 ms
k2-_5423d425-f9e8-4480-867d-ad430e1f436d.v1.css
357 ms
fqp0lia-d.css
354 ms
beacon.gif
155 ms
beacon.gif
152 ms
beacon.gif
153 ms
beacon.gif
149 ms
k2-_421024ab-4ac5-45d6-b35f-9744cc301d55.v1.gif
133 ms
pixel.gif
125 ms
k2-_646ff9c2-2d86-4ddf-b508-ed21f552840d.v1.jpg
57 ms
s69456323701888
18 ms
pixel.gif
12 ms
walmart.aspx
51 ms
k2-_3a501a0a-a4cd-4c2f-bb48-350e0b556f40.v1.jpg
20 ms
k2-_7cbb198a-1458-421f-a09c-4ac5af89b9b6.v1.jpg
13 ms
pixel
21 ms
cookiematch.aspx
21 ms
pixel
18 ms
uuid
195 ms
activeview
12 ms
8153628749607210664
200 ms
rum.gif
97 ms
mobile.walmart.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.walmart.com 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 Mobile.walmart.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.
mobile.walmart.com
Open Graph description is not detected on the main page of Mobile Walmart. 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: