2.4 sec in total
494 ms
1.2 sec
633 ms
Visit moto.com now to see the best up-to-date Moto content for Sweden and also check out these interesting facts you probably never knew about moto.com
#hellomoto | Discover our new unlocked Android phones from motorola and stay informed about our offers and promotions.
Visit moto.comWe analyzed Moto.com page load time and found that the first response time was 494 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
moto.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value23.8 s
0/100
25%
Value14.4 s
1/100
10%
Value7,350 ms
0/100
30%
Value0.679
8/100
15%
Value29.8 s
0/100
10%
494 ms
41 ms
60 ms
57 ms
37 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Moto.com, 2% (3 requests) were made to Io.vtex.com.br and 2% (3 requests) were made to Motorolaimgrepo.vteximg.com.br. The less responsive or slowest element that took the longest time to load (494 ms) relates to the external source Motorola.com.
Page size can be reduced by 1.8 MB (55%)
3.4 MB
1.5 MB
In fact, the total size of Moto.com main page is 3.4 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. 80% 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. HTML takes 2.1 MB which makes up the majority of the site volume.
Potential reduce by 1.8 MB
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 1.8 MB or 87% of the original size.
Potential reduce by 11.1 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. Moto images are well optimized though.
Potential reduce by 227 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 500 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. Moto.com has all CSS files already compressed.
Number of requests can be reduced by 89 (75%)
118
29
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Moto. 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 52 to 1 for CSS and as a result speed up the page load time.
494 ms
asset.min.css
41 ms
motorolaus.motorola-registration@0.3.7$style.common.min.css
60 ms
motorolaus.motorola-registration@0.3.7$style.small.min.css
57 ms
motorolaus.motorola-registration@0.3.7$style.notsmall.min.css
37 ms
motorolaus.motorola-registration@0.3.7$style.large.min.css
58 ms
motorolaus.motorola-registration@0.3.7$style.xlarge.min.css
66 ms
common.min.css
69 ms
HeaderRedesign.min.css
71 ms
MotoStoreWrapper.min.css
70 ms
0.min.css
74 ms
Footer.min.css
74 ms
Carousel.min.css
75 ms
ShelvesTabs.min.css
76 ms
GridLayout.min.css
75 ms
TrendingShelf.min.css
72 ms
SearchBottom.min.css
80 ms
Spinner.min.css
80 ms
Newsletter.min.css
79 ms
Disclaimers.min.css
81 ms
NotificationBarRedesign.min.css
79 ms
NavigationBarRedesign.min.css
79 ms
Subnav.min.css
84 ms
Minicart.min.css
81 ms
1.min.css
83 ms
1.min.css
83 ms
4.min.css
82 ms
SearchBar.min.css
81 ms
3.min.css
85 ms
Tooltip.min.css
84 ms
27.min.css
84 ms
FOC.min.css
85 ms
EnquiryForm.min.css
85 ms
17.min.css
89 ms
MotoRegModal.min.css
87 ms
HighlightOverlay.min.css
85 ms
css
71 ms
forms2.min.js
131 ms
index.min.css
54 ms
font-awesome.min.css
65 ms
TrendingBadges.min.css
35 ms
Autocomplete.min.css
38 ms
DiscountBadge.min.css
38 ms
ProductSummaryImage.min.css
33 ms
15.min.css
27 ms
SKUSelector.min.css
29 ms
Container.min.css
27 ms
0.min.css
27 ms
vtex.product-list@0.37.1$overrides.css
29 ms
vtex.minicart@2.67.1$overrides.css
24 ms
motorolaus.motorola-store-components@1.0.47$overrides.css
25 ms
motorolaus.motorola-store-theme@4.27.28$overrides.css
29 ms
vtex.checkout-container@0.8.0$overrides.css
26 ms
vtex.checkout-cart@0.35.3$overrides.css
27 ms
rc.js
263 ms
af.js
262 ms
gtm.js
290 ms
QR4MV-WWCTC-337JB-3LT7K-9RBLH
270 ms
Moto-g-Power-5G-pdp-ecom-render-5-color-1-166ljejx.png
244 ms
moto-g-5G-ecom-render-1-sedona-sage-6jsibwb7.png
252 ms
motorola-g-play-2024-ecom-render-1-sapphire-blue-axdwcq6e.png
245 ms
7b705631-bf86-467f-91f3-e6a49b76c879___6215ed1fa3478b0f60758e76525112ce.jpg
253 ms
e4ab9c51-7100-4416-9288-322dc3258de8___9f1ab72b0782574bb12ea72e1d1011ad.jpg
240 ms
59c41a23-11a2-46c9-a181-272026c26233___548dbb3c86aa1f749908f51dc01abd15.jpg
240 ms
164590-500-auto
248 ms
razr-40-ultra-bose-ecom-render-phantom-black-1-withtext.png
248 ms
razr-40-ultra-bose-ecom-render-viva-magenta-1-withtext.png
253 ms
razr-40-ultra-bose-ecom-render-saltwater-slide-2-withtext.png
316 ms
venus-bosebundle-withtext.png
316 ms
164593-500-auto
317 ms
tabletkeybundlecanyon-withtext.png
315 ms
164597-500-auto
361 ms
london-bosebundle.png
360 ms
163784-500-auto
359 ms
razr-ecom-render-1-sedona-.png
359 ms
razr-ecom-render-6-tofu-.png
358 ms
razr-ecom-render-11-grape-.png
359 ms
razr-ecom-render-16-mauve-chalk-.png
385 ms
164384-500-auto
363 ms
Moto-g-Power-5G-pdp-ecom-render-5-color-1-166ljejx.png
386 ms
Moto-g-Power-5G-pdp-ecom-render-16-color-2-m83ve0gy.png
386 ms
Icon-arrow-back-1.svg
275 ms
newsletter-d-bg.svg
264 ms
ico-flags-sprite.png
269 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
268 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff
270 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
293 ms
polyfill.min.js
216 ms
polyfill.min.js
381 ms
index.min.js
127 ms
runtime.js
127 ms
prop-types.min.js
152 ms
react.production.min.js
151 ms
react-dom.production.min.js
153 ms
react-dom-server.browser.production.min.js
153 ms
react-intl.min.js
154 ms
history.min.js
154 ms
ramda.min.js
152 ms
ls.unveilhooks.min.js
153 ms
lazysizes.min.js
156 ms
cssrelpreload.min.js
156 ms
common.min.js
172 ms
graphql.min.js
154 ms
apollo.min.js
151 ms
index.min.js
151 ms
asset.min.js
181 ms
asset.min.js
180 ms
asset.min.js
179 ms
asset.min.js
177 ms
asset.min.js
175 ms
asset.min.js
175 ms
config.json
140 ms
asset.min.js
118 ms
asset.min.js
117 ms
asset.min.js
119 ms
btt.js
189 ms
motorola.js
78 ms
loader
267 ms
asset.min.js
82 ms
asset.min.js
75 ms
asset.min.js
73 ms
bv.js
102 ms
moto.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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
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
moto.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
Serves images with low resolution
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
moto.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Moto.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 Moto.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.
moto.com
Open Graph data is detected on the main page of Moto. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: