3.3 sec in total
393 ms
2.8 sec
108 ms
Welcome to next.mx homepage info - get ready to check Next best content right away, or after learning these important things about next.mx
Shop the latest women's, men's and children's fashion plus homeware, beauty and more. Next day delivery and free returns available. Shop now!
Visit next.mxWe analyzed Next.mx page load time and found that the first response time was 393 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
next.mx performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value5.6 s
17/100
25%
Value5.1 s
61/100
10%
Value770 ms
38/100
30%
Value0
100/100
15%
Value5.4 s
72/100
10%
393 ms
144 ms
125 ms
96 ms
315 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that all of those requests were addressed to Next.mx and no external sources were called. The less responsive or slowest element that took the longest time to load (842 ms) relates to the external source Nextdirect.com.
Page size can be reduced by 540.0 kB (53%)
1.0 MB
477.4 kB
In fact, the total size of Next.mx main page is 1.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. 30% of websites need less resources to load. Javascripts take 490.7 kB which makes up the majority of the site volume.
Potential reduce by 75.3 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 37.7 kB, which is 47% 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 75.3 kB or 95% of the original size.
Potential reduce by 37.6 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. Obviously, Next needs image optimization as it can save up to 37.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 312.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 312.8 kB or 64% of the original size.
Potential reduce by 114.3 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. Next.mx needs all CSS files to be minified and compressed as it can save up to 114.3 kB or 44% of the original size.
Number of requests can be reduced by 117 (85%)
138
21
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Next. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
CountrySelect
393 ms
common.css
144 ms
CountrySelector.css
125 ms
jquery-3.4.0.js
96 ms
OverrideStyle.css
315 ms
Fonts.min.css
117 ms
c3FQUmYww
56 ms
m-flag-United-Kingdom.png
86 ms
m-flag-Ireland.png
26 ms
m-flag-Germany.png
65 ms
m-flag-Saudi-Arabia.png
105 ms
m-flag-Israel.png
76 ms
m-flag-United-Arab-Emirates.png
146 ms
m-flag-Ukraine.png
224 ms
m-flag-Australia.png
272 ms
m-flag-Kuwait.png
227 ms
m-flag-USA.png
195 ms
m-flag-Poland.png
171 ms
m-flag-Hong-Kong.png
240 ms
m-flag-Argentina.png
266 ms
m-flag-Brazil.png
437 ms
m-flag-Canada.png
369 ms
m-flag-Chile.png
350 ms
m-flag-Costa-Rica.png
364 ms
m-flag-Dominican-Republic.png
331 ms
m-flag-El-Salvador.png
385 ms
m-flag-Haiti.png
425 ms
m-flag-Jamaica.png
455 ms
m-flag-Mexico.png
472 ms
m-flag-Nicaragua.png
476 ms
m-flag-Panama.png
511 ms
m-flag-Peru.png
574 ms
m-flag-Puerto-Rico.png
551 ms
m-flag-Trinidad-and-Tobago.png
565 ms
m-flag-Bangladesh.png
592 ms
m-flag-Cambodia.png
523 ms
m-flag-China.png
635 ms
m-flag-India.png
650 ms
m-flag-Indonesia.png
683 ms
m-flag-Japan.png
618 ms
m-flag-Kazakhstan.png
703 ms
m-flag-Kyrgyzstan.png
699 ms
m-flag-Macau.png
693 ms
m-flag-Malaysia.png
732 ms
m-flag-Mongolia.png
757 ms
m-flag-Nepal.png
798 ms
m-flag-New-Zealand.png
628 ms
CountrySelect
842 ms
m-flag-Pakistan.png
613 ms
m-flag-Papua-New-Guinea.png
601 ms
m-flag-Philippines.png
678 ms
m-flag-Singapore.png
755 ms
m-flag-South-Korea.png
801 ms
m-flag-Sri-Lanka.png
732 ms
m-flag-Taiwan.png
684 ms
m-flag-Tajikistan.png
756 ms
m-flag-Thailand.png
744 ms
m-flag-Timor-Leste.png
704 ms
m-flag-Vietnam.png
664 ms
m-flag-Albania.png
695 ms
m-flag-Armenia.png
660 ms
m-flag-Austria.png
684 ms
m-flag-Azerbaijan.png
641 ms
m-flag-Belarus.png
722 ms
m-flag-Belgium.png
688 ms
m-flag-Bosnia-and-Herzegovina.png
675 ms
m-flag-Bulgaria.png
603 ms
m-flag-Croatia.png
577 ms
m-flag-Cyprus.png
638 ms
m-flag-Czech-Republic.png
635 ms
m-flag-Denmark.png
610 ms
m-flag-Estonia.png
624 ms
m-flag-Finland.png
657 ms
m-flag-France.png
644 ms
m-flag-Georgia.png
672 ms
m-flag-Gibraltar.png
549 ms
m-flag-Greece.png
626 ms
m-flag-Hungary.png
572 ms
m-flag-Iceland.png
554 ms
m-flag-Italy.png
594 ms
m-flag-Latvia.png
596 ms
m-flag-Lithuania.png
620 ms
m-flag-Luxembourg.png
556 ms
m-flag-Macedonia.png
548 ms
m-flag-Malta.png
581 ms
m-flag-Netherlands.png
588 ms
m-flag-Norway.png
523 ms
m-flag-Portugal.png
455 ms
m-flag-Republic-of-Moldova.png
533 ms
m-flag-Romania.png
455 ms
m-flag-Serbia.png
425 ms
m-flag-Slovakia.png
577 ms
AzoSans-Light-webfont.woff
475 ms
AzoSans-Regular-webfont.woff
444 ms
AzoSans-Medium.woff
508 ms
AzoSans-Thin-webfont.woff
474 ms
m-flag-Slovenia.png
480 ms
m-flag-Spain.png
526 ms
m-flag-Sweden.png
508 ms
m-flag-Switzerland.png
494 ms
m-flag-T%C3%BCrkiye.png
573 ms
m-flag-British-Forces-Post-Office.png
513 ms
m-flag-Algeria.png
494 ms
m-flag-Angola.png
542 ms
m-flag-Bahrain.png
571 ms
m-flag-Botswana.png
519 ms
m-flag-Burkina-Faso.png
486 ms
m-flag-Cameroon.png
564 ms
m-flag-Central-African-Republic.png
619 ms
m-flag-Chad.png
451 ms
m-flag-Egypt.png
488 ms
m-flag-Equatorial-Guinea.png
519 ms
m-flag-Eswatini.png
481 ms
m-flag-Ethiopia.png
553 ms
m-flag-Gabon.png
550 ms
m-flag-Gambia.png
486 ms
m-flag-Ghana.png
519 ms
m-flag-Guinea.png
472 ms
m-flag-Guinea-Bissau.png
524 ms
m-flag-Jordan.png
465 ms
m-flag-Kenya.png
477 ms
m-flag-Lebanon.png
471 ms
m-flag-Lesotho.png
519 ms
m-flag-Madagascar.png
448 ms
m-flag-Malawi.png
503 ms
m-flag-Mali.png
448 ms
m-flag-Mauritania.png
457 ms
m-flag-Mauritius.png
440 ms
m-flag-Morocco.png
507 ms
m-flag-Mozambique.png
419 ms
m-flag-Namibia.png
472 ms
m-flag-Niger.png
448 ms
m-flag-Nigeria.png
435 ms
m-flag-Oman.png
463 ms
m-flag-Qatar.png
466 ms
m-flag-Rwanda.png
489 ms
m-flag-Senegal.png
422 ms
m-flag-Sierra-Leone.png
449 ms
m-flag-South-Africa.png
447 ms
m-flag-Togo.png
420 ms
m-flag-Uganda.png
447 ms
m-flag-Zambia.png
441 ms
sprites-white.png
466 ms
icon-ui-chevron.svg
377 ms
next.mx accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
next.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
next.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Next.mx 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 Next.mx 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.
next.mx
Open Graph description is not detected on the main page of Next. 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: