3.1 sec in total
134 ms
2.4 sec
541 ms
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 134 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.
osmoz.com.br performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value16.0 s
0/100
25%
Value13.5 s
2/100
10%
Value2,060 ms
7/100
30%
Value0.011
100/100
15%
Value24.5 s
0/100
10%
134 ms
142 ms
232 ms
142 ms
139 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 56% of them (64 requests) were addressed to the original Osmoz.com.br, 10% (11 requests) were made to Googleads.g.doubleclick.net and 7% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (993 ms) belongs to the original domain Osmoz.com.br.
Page size can be reduced by 571.4 kB (13%)
4.3 MB
3.7 MB
In fact, the total size of Osmoz.com.br main page is 4.3 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 88.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 13.8 kB, which is 13% 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 88.7 kB or 81% of the original size.
Potential reduce by 457.8 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 457.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 22.4 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.com.br 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 45 (44%)
102
57
The browser has sent 102 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 28 to 1 for JavaScripts and as a result speed up the page load time.
osmoz.com.br
134 ms
osmoz.com.br
142 ms
www.osmoz.com.br
232 ms
jquery.js
142 ms
global.css
139 ms
adsbygoogle.js
162 ms
home.js
162 ms
facebook.init.js
76 ms
all.js
19 ms
site.un.js
160 ms
show_ads_impl.js
303 ms
async-ads.js
113 ms
gpt.js
180 ms
line.jpg
133 ms
all.js
15 ms
ga.js
72 ms
logo_sprite.png
138 ms
arrow_header.png
121 ms
search_picto.png
131 ms
power.png
69 ms
banner_hp_brazil_osmoz_6fcdfb553d.jpg
273 ms
shadow_une.png
112 ms
arrow_r.png
271 ms
probiotico_1_e21475df9d.jpeg
128 ms
black_shadow1.png
273 ms
perfumes_mais_cheirosos_do_mundo_0fb0d1fe49.jpg
146 ms
can_you_bring_perfume_on_a_plane_745575265c_31a4871f4d.jpg
275 ms
black_shadow2.png
352 ms
eye.png
192 ms
melhores_perfume_masculinos_782921810b.jpg
200 ms
perfume_big.jpg
216 ms
imagem_perfume_diva_rouge_e415e4789b.jpg
273 ms
white_shadow.png
380 ms
imagem_perfume_jelly_candy_587ec79e42.jpg
425 ms
imagem_perfume_lollipop_candy_352a900f31.jpg
403 ms
essential_lacoste_fragrance_88563f0def.jpg
274 ms
imagem_perfume_elas_rock_party_139da795e4.jpg
431 ms
imagen_perfume_elas_pop_day_a29b8c4d29.jpg
349 ms
imagem_perfume_abyssal_3724a7df14.jpg
350 ms
imagem_perfume_royal_madeira_c7fd10a18f.jpg
352 ms
imagem_perfume_uzon_black_b39ef3fd08.jpg
459 ms
imagem_perfume_uzon4x4_bc394e4bb4.jpg
352 ms
67dd8fe1.jpg
352 ms
arrow2.png
488 ms
imagem_fragrance_diva_purpura_1cb5a1f32c.jpg
521 ms
member_small.jpg
518 ms
la_vie_est_belle_l_eau_de_toilette_lancome_3bcb33e6dd.jpg
625 ms
2173476_a8beb28161.jpg
622 ms
image_fragrance_armani_code_for_her_ece37dc865.jpg
931 ms
rioqueanima_o_boticario_c75966408b.jpg
510 ms
arrow_l.png
523 ms
91 ms
Novecentowide-Medium-webfont.woff
575 ms
__utm.gif
28 ms
__utm.gif
24 ms
Novecentowide-DemiBold-webfont.woff
557 ms
SinkinSans-200XLight-webfont.woff
539 ms
SinkinSans-500Medium-webfont.woff
634 ms
member_big.jpg
640 ms
2096799_44e9633181.jpg
993 ms
2006833_4babe98a63.jpg
525 ms
pubads_impl.js
27 ms
2088257_c665fd409d.jpg
647 ms
2058643_47cc6013dd.jpg
479 ms
2144796_6c2b63a677.jpg
479 ms
2100853_ed0a8dc7ee.jpg
436 ms
2112999_474fb9c5ea.jpg
450 ms
osmoz_logo.png
469 ms
footer_icon.png
595 ms
mobile_menu.png
519 ms
spinner_search.gif
583 ms
cross.png
611 ms
fb_button.png
582 ms
white_cross.png
929 ms
zrt_lookup.html
28 ms
ads
464 ms
main.js
295 ms
reactive_library.js
208 ms
ca-pub-5244826864777578
126 ms
ads
515 ms
ads
302 ms
ads
299 ms
ads
337 ms
ads
503 ms
load_preloaded_resource.js
45 ms
abg_lite.js
46 ms
s
40 ms
window_focus.js
43 ms
qs_click_protection.js
44 ms
ufs_web_display.js
31 ms
e92e9b19fdbae9b3a3ef41360efccaf5.js
162 ms
fullscreen_api_adapter.js
148 ms
interstitial_ad_frame.js
154 ms
pixel
153 ms
dv3.js
176 ms
icon.png
151 ms
gen_204
150 ms
feedback_grey600_24dp.png
143 ms
settings_grey600_24dp.png
143 ms
css
64 ms
pixel
71 ms
getuid
77 ms
pixel
78 ms
ad
65 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
29 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
34 ms
setuid
19 ms
wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js
67 ms
abg_lite.js
65 ms
Q12zgMmT.js
64 ms
pixel
105 ms
rum
47 ms
rum
29 ms
62bHydCX.html
14 ms
osmoz.com.br 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.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: