7 sec in total
373 ms
5.6 sec
1.1 sec
Visit osmoz.com.br now to see the best up-to-date OSMOZ content for Brazil and also check out these interesting facts you probably never knew about osmoz.com.br
Fale de seus perfumes preferidos, parta ao encontro de seu próximo perfume e ganhe presentes, em OSMOZ.
Visit osmoz.com.brWe analyzed Osmoz.com.br page load time and found that the first response time was 373 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
osmoz.com.br performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value20.1 s
0/100
25%
Value9.5 s
12/100
10%
Value1,660 ms
11/100
30%
Value0
100/100
15%
Value20.1 s
2/100
10%
373 ms
2495 ms
165 ms
388 ms
158 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 61% of them (60 requests) were addressed to the original Osmoz.com.br, 10% (10 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Osmoz.com.br.
Page size can be reduced by 909.5 kB (15%)
6.2 MB
5.2 MB
In fact, the total size of Osmoz.com.br main page is 6.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. 75% 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. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 68.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 13.7 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 68.3 kB or 79% of the original size.
Potential reduce by 482.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. OSMOZ images are well optimized though.
Potential reduce by 182.6 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 182.6 kB or 51% of the original size.
Potential reduce by 176.5 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.br needs all CSS files to be minified and compressed as it can save up to 176.5 kB or 90% of the original size.
Number of requests can be reduced by 30 (33%)
92
62
The browser has sent 92 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 20 to 1 for JavaScripts and as a result speed up the page load time.
osmoz.com.br
373 ms
www.osmoz.com.br
2495 ms
ads.js
165 ms
jquery.js
388 ms
home.js
158 ms
global.css
654 ms
adsbygoogle.js
7 ms
ajs.php
248 ms
facebook.init.js
83 ms
all.js
8 ms
site.js
163 ms
async-ads.js
79 ms
gpt.js
29 ms
imagem_perfume_diva_rouge_e415e4789b.jpg
140 ms
imagem_perfume_jelly_candy_587ec79e42.jpg
288 ms
imagem_perfume_lollipop_candy_352a900f31.jpg
137 ms
essential_lacoste_fragrance_88563f0def.jpg
287 ms
imagem_perfume_elas_rock_party_139da795e4.jpg
139 ms
imagen_perfume_elas_pop_day_a29b8c4d29.jpg
302 ms
imagem_perfume_abyssal_3724a7df14.jpg
304 ms
imagem_perfume_royal_madeira_c7fd10a18f.jpg
336 ms
imagem_perfume_uzon_black_b39ef3fd08.jpg
283 ms
imagem_perfume_uzon4x4_bc394e4bb4.jpg
337 ms
imagem_fragrance_diva_purpura_1cb5a1f32c.jpg
303 ms
l_homme_parfum_intense_yves_saint_laurent_700976bb6d.jpg
380 ms
2096799_a7d8f28711.jpg
743 ms
172c61d2.jpg
465 ms
ef7c3dd0.jpg
384 ms
2161760_87e883f52f.jpg
732 ms
709b2d12.jpg
407 ms
2122572_2390c1e7b3.jpg
533 ms
2006833_4babe98a63.jpg
546 ms
2119162_2fe413ff9e.jpg
1308 ms
2088257_c665fd409d.jpg
1299 ms
2058643_47cc6013dd.jpg
1270 ms
2144796_6c2b63a677.jpg
729 ms
2100853_ed0a8dc7ee.jpg
892 ms
2112999_474fb9c5ea.jpg
924 ms
line.jpg
807 ms
logo_sprite.png
885 ms
arrow_header.png
964 ms
search_picto.png
962 ms
power.png
993 ms
z_64bb16551a.jpg
1440 ms
shadow_une.png
1246 ms
arrow_r.png
1071 ms
aaaaaaaaaaa_af2ae9272a.jpg
1303 ms
black_shadow1.png
1326 ms
image_parfum_couv_480dafcbd2.jpg
1416 ms
antenna.ayads.co
245 ms
pubads_impl_82.js
64 ms
antenna.ayads.co
229 ms
antenna.ayads.co
232 ms
ga.js
84 ms
Novecentowide-Medium-webfont.woff
1252 ms
Novecentowide-DemiBold-webfont.woff
1262 ms
2fa30669-9bbd-4ced-912f-db94a367ed6c.woff
1287 ms
ads
139 ms
container.html
92 ms
167 ms
__utm.gif
53 ms
__utm.gif
53 ms
70ae52ec-d89b-4c6a-9402-854ebe423c54.woff
1150 ms
image_parfum_rochas_90ans_couv_d66721f592.png
1834 ms
xd_arbiter.php
49 ms
xd_arbiter.php
68 ms
black_shadow2.png
1182 ms
eye.png
1177 ms
10_roses_couv_71532f60e2.jpg
1895 ms
perfume_big.jpg
1203 ms
white_shadow.png
1182 ms
arrow2.png
1219 ms
osd.js
7 ms
like_box.php
204 ms
member_small.jpg
1173 ms
arrow_l.png
1198 ms
member_big.jpg
1188 ms
osmoz_logo.png
1167 ms
xd_arbiter.php
9 ms
footer_icon.png
1104 ms
350x250.jpg
425 ms
ebiMDO3r-8l.css
21 ms
jGc-59L_9lo.css
25 ms
TKuNj0xVh4A.js
40 ms
8w-1WQE8wsO.js
65 ms
0wM5s1Khldu.js
36 ms
1bNoFZUdlYZ.js
63 ms
12321105_10153439110018472_1535902885554905605_n.jpg
77 ms
1452497_10151870205378472_1262956138_n.jpg
26 ms
67219_1488666618070624_3833715835670704347_n.jpg
27 ms
9611_146633332394383_6724397605047896941_n.jpg
28 ms
12647239_1689983971277932_1022932728707642786_n.jpg
27 ms
1554398_10156721889795118_9091328641774812461_n.jpg
30 ms
10456012_10208396476288371_4276577075471376093_n.jpg
28 ms
wL6VQj7Ab77.png
24 ms
s7jcwEQH7Sx.png
24 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
5 ms
osmoz.com.br 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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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.com.br 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
Browser errors were logged to the console
Page has valid source maps
osmoz.com.br SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Osmoz.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Osmoz.com.br 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.com.br
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: