2.6 sec in total
353 ms
1.7 sec
542 ms
Welcome to osmoz.it homepage info - get ready to check OSMOZ best content right away, or after learning these important things about osmoz.it
Talk about your favourite perfumes, hunt down your next fragrance and win numerous gifts on OSMOZ!
Visit osmoz.itWe analyzed Osmoz.it page load time and found that the first response time was 353 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
osmoz.it performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value10.1 s
0/100
25%
Value10.5 s
7/100
10%
Value560 ms
53/100
30%
Value0.002
100/100
15%
Value18.9 s
3/100
10%
353 ms
61 ms
146 ms
15 ms
33 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Osmoz.it, 86% (59 requests) were made to Osmoz.com and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (727 ms) relates to the external source Osmoz.com.
Page size can be reduced by 434.3 kB (13%)
3.2 MB
2.8 MB
In fact, the total size of Osmoz.it main page is 3.2 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. 50% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 83.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 16.6 kB, which is 16% 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 83.7 kB or 80% of the original size.
Potential reduce by 346.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. Obviously, OSMOZ needs image optimization as it can save up to 346.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.6 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. Osmoz.it needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 11% of the original size.
Number of requests can be reduced by 16 (26%)
61
45
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OSMOZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
osmoz.it
353 ms
www.osmoz.com
61 ms
www.osmoz.com
146 ms
jquery.js
15 ms
global.css
33 ms
home.js
27 ms
js
65 ms
facebook.init.js
130 ms
all.js
27 ms
site.un.js
140 ms
line.jpg
11 ms
logo_sprite.png
119 ms
arrow_header.png
119 ms
search_picto.png
119 ms
power.png
136 ms
best_cologne_for_men_6364004006_448e105b2c.jpg
131 ms
shadow_une.png
136 ms
arrow_r.png
232 ms
coffee_scented_candles_c3bcbb19d3.jpg
248 ms
black_shadow1.png
228 ms
scented_sachets_07d021bffd.jpg
253 ms
apple_blossom_scented_candles_48ecb3db7d.jpg
253 ms
black_shadow2.png
255 ms
eye.png
340 ms
orange_scented_candles_c287ff98b3.jpg
360 ms
perfume_big.jpg
358 ms
fragrance_capricci_nina_ricci_48cf71aafa.jpg
366 ms
white_shadow.png
362 ms
6a309b73.jpg
370 ms
5545968e.jpg
458 ms
101c2233.jpg
472 ms
801836c7.jpg
470 ms
f3fcfafd.jpg
473 ms
b09bc3a6.jpg
471 ms
8ffdbf87.jpg
482 ms
4e7a40d8.gif
571 ms
bfea18da.jpg
589 ms
2f5fa70b.jpg
587 ms
arrow2.png
627 ms
fd8750ef.jpg
596 ms
member_small.jpg
589 ms
36e43df9.jpg
680 ms
2059221_original.jpg
701 ms
narciso_poudre_4a18c0b309.jpg
704 ms
all.js
10 ms
64461_b2d6309f15.jpg
698 ms
m9511405_p1977044_princ_hero_4762901904.jpg
697 ms
ga.js
22 ms
arrow_l.png
727 ms
96 ms
advertising.js
59 ms
__utm.gif
12 ms
__utm.gif
17 ms
collect
27 ms
Novecentowide-Medium-webfont.woff
691 ms
Novecentowide-DemiBold-webfont.woff
710 ms
SinkinSans-200XLight-webfont.woff
697 ms
SinkinSans-500Medium-webfont.woff
682 ms
member_big.jpg
685 ms
2096799_44e9633181.jpg
642 ms
2006833_4babe98a63.jpg
695 ms
2088257_c665fd409d.jpg
682 ms
2058643_47cc6013dd.jpg
682 ms
2144796_6c2b63a677.jpg
687 ms
2100853_ed0a8dc7ee.jpg
682 ms
2112999_474fb9c5ea.jpg
645 ms
osmoz_logo.png
676 ms
footer_icon.png
677 ms
main.js
251 ms
osmoz.it accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
osmoz.it 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
osmoz.it 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Osmoz.it 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 Osmoz.it 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.
osmoz.it
Open Graph description is not detected on the main page of OSMOZ. 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: