2.4 sec in total
480 ms
1.9 sec
98 ms
Click here to check amazing Next content for Oman. Otherwise, check out these important facts you probably never knew about next.om
Shop the latest women's, men's and children's fashion plus homeware, beauty and more. FREE* and fast delivery available. Shop now!
Visit next.omWe analyzed Next.om page load time and found that the first response time was 480 ms and then it took 2 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.
next.om performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value4.6 s
35/100
25%
Value3.8 s
84/100
10%
Value130 ms
96/100
30%
Value0
100/100
15%
Value3.8 s
89/100
10%
480 ms
166 ms
87 ms
150 ms
325 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.om and no external sources were called. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Nextdirect.com.
Page size can be reduced by 540.0 kB (53%)
1.0 MB
470.8 kB
In fact, the total size of Next.om 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. 35% of websites need less resources to load. Javascripts take 484.2 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 65% 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.om 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
480 ms
common.css
166 ms
CountrySelector.css
87 ms
jquery-3.4.0.js
150 ms
OverrideStyle.css
325 ms
Fonts.min.css
101 ms
CW1Bfflw
49 ms
m-flag-United-Kingdom.png
12 ms
m-flag-Ireland.png
26 ms
m-flag-Germany.png
11 ms
m-flag-Saudi-Arabia.png
13 ms
m-flag-Israel.png
36 ms
m-flag-United-Arab-Emirates.png
20 ms
m-flag-Ukraine.png
21 ms
m-flag-Australia.png
21 ms
m-flag-Kuwait.png
28 ms
m-flag-USA.png
33 ms
m-flag-Poland.png
30 ms
m-flag-Hong-Kong.png
93 ms
m-flag-Argentina.png
36 ms
m-flag-Brazil.png
91 ms
m-flag-Canada.png
91 ms
m-flag-Chile.png
422 ms
m-flag-Costa-Rica.png
90 ms
m-flag-Dominican-Republic.png
102 ms
m-flag-El-Salvador.png
145 ms
m-flag-Haiti.png
109 ms
m-flag-Jamaica.png
110 ms
m-flag-Mexico.png
117 ms
m-flag-Nicaragua.png
126 ms
m-flag-Panama.png
120 ms
m-flag-Peru.png
126 ms
m-flag-Puerto-Rico.png
129 ms
m-flag-Trinidad-and-Tobago.png
136 ms
m-flag-Bangladesh.png
136 ms
m-flag-Cambodia.png
150 ms
m-flag-China.png
144 ms
m-flag-India.png
145 ms
m-flag-Indonesia.png
145 ms
m-flag-Japan.png
258 ms
m-flag-Kazakhstan.png
182 ms
m-flag-Kyrgyzstan.png
207 ms
m-flag-Macau.png
275 ms
m-flag-Malaysia.png
585 ms
m-flag-Mongolia.png
200 ms
m-flag-Nepal.png
203 ms
m-flag-New-Zealand.png
203 ms
m-flag-Pakistan.png
219 ms
m-flag-Papua-New-Guinea.png
211 ms
m-flag-Philippines.png
428 ms
m-flag-Singapore.png
400 ms
m-flag-South-Korea.png
257 ms
m-flag-Sri-Lanka.png
340 ms
m-flag-Taiwan.png
271 ms
m-flag-Tajikistan.png
335 ms
m-flag-Thailand.png
297 ms
m-flag-Timor-Leste.png
409 ms
m-flag-Vietnam.png
483 ms
m-flag-Albania.png
406 ms
m-flag-Armenia.png
396 ms
m-flag-Austria.png
357 ms
m-flag-Azerbaijan.png
362 ms
m-flag-Belarus.png
370 ms
m-flag-Belgium.png
376 ms
m-flag-Bosnia-and-Herzegovina.png
472 ms
m-flag-Bulgaria.png
394 ms
CountrySelect
661 ms
m-flag-Croatia.png
387 ms
m-flag-Cyprus.png
399 ms
m-flag-Czech-Republic.png
464 ms
m-flag-Denmark.png
465 ms
m-flag-Estonia.png
448 ms
m-flag-Finland.png
558 ms
m-flag-France.png
469 ms
m-flag-Georgia.png
426 ms
m-flag-Gibraltar.png
543 ms
m-flag-Greece.png
414 ms
m-flag-Hungary.png
400 ms
m-flag-Iceland.png
481 ms
m-flag-Italy.png
463 ms
m-flag-Latvia.png
405 ms
m-flag-Lithuania.png
403 ms
m-flag-Luxembourg.png
413 ms
m-flag-Macedonia.png
422 ms
m-flag-Malta.png
407 ms
m-flag-Netherlands.png
347 ms
m-flag-Norway.png
333 ms
m-flag-Portugal.png
299 ms
m-flag-Republic-of-Moldova.png
298 ms
m-flag-Romania.png
307 ms
m-flag-Serbia.png
281 ms
m-flag-Slovakia.png
280 ms
m-flag-Slovenia.png
254 ms
m-flag-Spain.png
251 ms
m-flag-Sweden.png
350 ms
m-flag-Switzerland.png
261 ms
m-flag-T%C3%BCrkiye.png
245 ms
m-flag-British-Forces-Post-Office.png
256 ms
m-flag-Algeria.png
234 ms
m-flag-Angola.png
238 ms
m-flag-Bahrain.png
231 ms
m-flag-Botswana.png
197 ms
m-flag-Burkina-Faso.png
183 ms
m-flag-Cameroon.png
183 ms
m-flag-Central-African-Republic.png
176 ms
m-flag-Chad.png
251 ms
m-flag-Egypt.png
176 ms
m-flag-Equatorial-Guinea.png
317 ms
m-flag-Eswatini.png
174 ms
m-flag-Ethiopia.png
239 ms
m-flag-Gabon.png
208 ms
m-flag-Gambia.png
190 ms
m-flag-Ghana.png
266 ms
m-flag-Guinea.png
184 ms
m-flag-Guinea-Bissau.png
195 ms
m-flag-Jordan.png
217 ms
m-flag-Kenya.png
274 ms
m-flag-Lebanon.png
182 ms
m-flag-Lesotho.png
293 ms
m-flag-Madagascar.png
193 ms
m-flag-Malawi.png
205 ms
m-flag-Mali.png
219 ms
m-flag-Mauritania.png
278 ms
m-flag-Mauritius.png
219 ms
m-flag-Morocco.png
217 ms
m-flag-Mozambique.png
293 ms
m-flag-Namibia.png
366 ms
m-flag-Niger.png
278 ms
m-flag-Nigeria.png
256 ms
m-flag-Oman.png
280 ms
m-flag-Qatar.png
264 ms
m-flag-Rwanda.png
352 ms
m-flag-Senegal.png
271 ms
m-flag-Sierra-Leone.png
293 ms
m-flag-South-Africa.png
278 ms
m-flag-Togo.png
334 ms
m-flag-Uganda.png
269 ms
m-flag-Zambia.png
338 ms
sprites-white.png
259 ms
icon-ui-chevron.svg
302 ms
AzoSans-Light-webfont.woff
236 ms
AzoSans-Regular-webfont.woff
246 ms
AzoSans-Medium.woff
256 ms
AzoSans-Thin-webfont.woff
267 ms
next.om 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.om 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.om 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.om 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.om 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.om
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: