Tools & Wizards About Us
osmoz.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

osmoz.com

OSMOZ – Perfumes to share, your new fragrance to discover!

Page Load Speed

2.7 sec in total

First Response

72 ms

Resources Loaded

2.1 sec

Page Rendered

507 ms

osmoz.com screenshot

About Website

Click here to check amazing OSMOZ content for Iran. Otherwise, check out these important facts you probably never knew about osmoz.com

Talk about your favourite perfumes, hunt down your next fragrance and win numerous gifts on OSMOZ!

Visit osmoz.com

Key Findings

We analyzed Osmoz.com page load time and found that the first response time was 72 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

osmoz.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value1,200 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

osmoz.com

72 ms

osmoz.com

142 ms

www.osmoz.com

158 ms

jquery.js

18 ms

global.css

41 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 75% of them (60 requests) were addressed to the original Osmoz.com, 11% (9 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Osmoz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.8 kB (13%)

Content Size

3.2 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Osmoz.com 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. 70% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 83.2 kB

  • Original 104.4 kB
  • After minification 87.8 kB
  • After compression 21.2 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.2 kB or 80% of the original size.

Image Optimization

-11%

Potential reduce by 346.0 kB

  • Original 3.0 MB
  • After minification 2.7 MB

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.

JavaScript Optimization

-3%

Potential reduce by 2.1 kB

  • Original 66.0 kB
  • After minification 66.0 kB
  • After compression 63.9 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.

CSS Optimization

-11%

Potential reduce by 2.6 kB

  • Original 23.9 kB
  • After minification 23.9 kB
  • After compression 21.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. Osmoz.com needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (33%)

Requests Now

72

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 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 17 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

osmoz.com

osmoz.com

72 ms

osmoz.com

osmoz.com

142 ms

www.osmoz.com

www.osmoz.com

158 ms

jquery.js

jquery.js

18 ms

global.css

global.css

41 ms

home.js

home.js

165 ms

js

js

91 ms

facebook.init.js

facebook.init.js

55 ms

all.js

all.js

59 ms

site.un.js

site.un.js

162 ms

all.js

all.js

48 ms

ga.js

ga.js

72 ms

line.jpg

line.jpg

118 ms

logo_sprite.png

logo_sprite.png

122 ms

arrow_header.png

arrow_header.png

168 ms

search_picto.png

search_picto.png

176 ms

power.png

power.png

118 ms

best_cologne_for_men_6364004006_448e105b2c.jpg

best_cologne_for_men_6364004006_448e105b2c.jpg

164 ms

shadow_une.png

shadow_une.png

319 ms

arrow_r.png

arrow_r.png

321 ms

coffee_scented_candles_c3bcbb19d3.jpg

coffee_scented_candles_c3bcbb19d3.jpg

317 ms

black_shadow1.png

black_shadow1.png

321 ms

scented_sachets_07d021bffd.jpg

scented_sachets_07d021bffd.jpg

324 ms

apple_blossom_scented_candles_48ecb3db7d.jpg

apple_blossom_scented_candles_48ecb3db7d.jpg

324 ms

black_shadow2.png

black_shadow2.png

352 ms

eye.png

eye.png

614 ms

orange_scented_candles_c287ff98b3.jpg

orange_scented_candles_c287ff98b3.jpg

483 ms

perfume_big.jpg

perfume_big.jpg

454 ms

fragrance_capricci_nina_ricci_48cf71aafa.jpg

fragrance_capricci_nina_ricci_48cf71aafa.jpg

435 ms

white_shadow.png

white_shadow.png

500 ms

6a309b73.jpg

6a309b73.jpg

480 ms

5545968e.jpg

5545968e.jpg

552 ms

101c2233.jpg

101c2233.jpg

586 ms

801836c7.jpg

801836c7.jpg

599 ms

f3fcfafd.jpg

f3fcfafd.jpg

657 ms

b09bc3a6.jpg

b09bc3a6.jpg

628 ms

8ffdbf87.jpg

8ffdbf87.jpg

668 ms

4e7a40d8.gif

4e7a40d8.gif

1011 ms

bfea18da.jpg

bfea18da.jpg

718 ms

2f5fa70b.jpg

2f5fa70b.jpg

718 ms

arrow2.png

arrow2.png

750 ms

fd8750ef.jpg

fd8750ef.jpg

777 ms

member_small.jpg

member_small.jpg

778 ms

36e43df9.jpg

36e43df9.jpg

834 ms

2059221_original.jpg

2059221_original.jpg

831 ms

narciso_poudre_4a18c0b309.jpg

narciso_poudre_4a18c0b309.jpg

869 ms

64461_b2d6309f15.jpg

64461_b2d6309f15.jpg

910 ms

m9511405_p1977044_princ_hero_4762901904.jpg

m9511405_p1977044_princ_hero_4762901904.jpg

868 ms

advertising.js

advertising.js

102 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

23 ms

like_box.php

like_box.php

96 ms

Novecentowide-Medium-webfont.woff

Novecentowide-Medium-webfont.woff

833 ms

Novecentowide-DemiBold-webfont.woff

Novecentowide-DemiBold-webfont.woff

836 ms

SinkinSans-200XLight-webfont.woff

SinkinSans-200XLight-webfont.woff

872 ms

collect

collect

27 ms

SinkinSans-500Medium-webfont.woff

SinkinSans-500Medium-webfont.woff

862 ms

arrow_l.png

arrow_l.png

913 ms

gzCy-hx--rE.css

gzCy-hx--rE.css

22 ms

x6r42IOOUZz.js

x6r42IOOUZz.js

27 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

25 ms

O9zq51FKpXz.js

O9zq51FKpXz.js

25 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

25 ms

qwSlV7K_jlE.js

qwSlV7K_jlE.js

23 ms

zYzGplAqD4J.js

zYzGplAqD4J.js

56 ms

p55HfXW__mM.js

p55HfXW__mM.js

57 ms

304843289_514763520652222_1539993805453196142_n.jpg

304843289_514763520652222_1539993805453196142_n.jpg

35 ms

304945382_514763523985555_6191127465369199982_n.jpg

304945382_514763523985555_6191127465369199982_n.jpg

12 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

10 ms

member_big.jpg

member_big.jpg

748 ms

2096799_44e9633181.jpg

2096799_44e9633181.jpg

747 ms

2006833_4babe98a63.jpg

2006833_4babe98a63.jpg

793 ms

2088257_c665fd409d.jpg

2088257_c665fd409d.jpg

811 ms

2058643_47cc6013dd.jpg

2058643_47cc6013dd.jpg

822 ms

2144796_6c2b63a677.jpg

2144796_6c2b63a677.jpg

857 ms

2100853_ed0a8dc7ee.jpg

2100853_ed0a8dc7ee.jpg

893 ms

2112999_474fb9c5ea.jpg

2112999_474fb9c5ea.jpg

854 ms

osmoz_logo.png

osmoz_logo.png

1074 ms

footer_icon.png

footer_icon.png

834 ms

main.js

main.js

237 ms

Accessibility Review

osmoz.com accessibility score

71

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

osmoz.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

osmoz.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osmoz.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 Osmoz.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.

Social Sharing Optimization

osmoz.com

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: