2.2 sec in total
140 ms
1.9 sec
128 ms
Visit ogilvy.com.br now to see the best up-to-date Ogilvy content for Brazil and also check out these interesting facts you probably never knew about ogilvy.com.br
Site da Ogilvy Brasil
Visit ogilvy.com.brWe analyzed Ogilvy.com.br page load time and found that the first response time was 140 ms and then it took 2.1 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.
ogilvy.com.br performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value13.6 s
0/100
25%
Value6.3 s
41/100
10%
Value220 ms
87/100
30%
Value0.618
10/100
15%
Value5.7 s
68/100
10%
140 ms
12 ms
9 ms
21 ms
41 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 74% of them (79 requests) were addressed to the original Ogilvy.com.br, 14% (15 requests) were made to Scontent.xx.fbcdn.net and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 583.8 kB (16%)
3.7 MB
3.1 MB
In fact, the total size of Ogilvy.com.br main page is 3.7 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. 80% 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.1 MB which makes up the majority of the site volume.
Potential reduce by 62.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.0 kB, which is 21% 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 62.2 kB or 81% of the original size.
Potential reduce by 198.2 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. Ogilvy images are well optimized though.
Potential reduce by 261.5 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 261.5 kB or 66% of the original size.
Potential reduce by 62.0 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. Ogilvy.com.br needs all CSS files to be minified and compressed as it can save up to 62.0 kB or 88% of the original size.
Number of requests can be reduced by 18 (18%)
99
81
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ogilvy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
ogilvy.com.br
140 ms
screen.css
12 ms
plugins.css
9 ms
modernizr-2.6.2.min.js
21 ms
js
41 ms
player_api
39 ms
jquery-1.9.1.min.js
83 ms
viewport.js
13 ms
plugins.min.js
78 ms
util.js
76 ms
www-widgetapi.js
177 ms
dc.js
180 ms
gtm.js
203 ms
all.js
309 ms
logo_ogilvy.png
173 ms
sprite-nav.png
160 ms
sprite_social-networks.png
157 ms
bg_sidebar-highlights-home.png
157 ms
burger-king-whopperface_p.jpg
159 ms
grupo-de-incentivo-a-vida-o-cartaz-hiv-positivo_p.jpg
170 ms
hellmanns-receita-na-notinha_p.jpg
170 ms
graacc-carequinhas_p.jpg
172 ms
cannes1.jpg
185 ms
cannes2.jpg
185 ms
cannes3_1.png
172 ms
cannes3_2.jpg
174 ms
billboard-brasil-parada-gay-na-radio_m.jpg
173 ms
graacc-help-line-de-desenhos-_m.jpg
174 ms
sol-de-janeiro-tatuadores-contra-o-cancer-de-pele_m.jpg
175 ms
sport-club-recife-fas-imortais_m.jpg
177 ms
coca-cola-cartas-esquecidas_m.jpg
176 ms
flying-horse-gatorrada_m.jpg
177 ms
coca-cola-refil-da-felicidade_m.jpg
178 ms
sport-club-recife-security-moms_m.jpg
179 ms
bg-news2.png
184 ms
cases-loader.gif
186 ms
bg_divine-discontent.png
189 ms
bg_image-people.png
179 ms
photo_sergio-amado.png
190 ms
photo_luiz-leite.png
184 ms
photo_fernando-musa.png
182 ms
photo_Claudio-Lima.png
185 ms
photo_luis-carlos-franco.png
188 ms
photo_felix-del-valle.png
185 ms
photo_daniel-de-tomazo.png
189 ms
photo_Flavio-De-Pauw.png
190 ms
photo_toni-ferreira.png
188 ms
photo_patricia-fuzzo.png
186 ms
raleway-medium.woff
186 ms
456 ms
artigos.json
46 ms
photo_sandra-azedo.png
43 ms
photo_renata-saraiva.png
42 ms
photo_denise-israel.png
40 ms
ogilvyjbaskerville-italic.woff
69 ms
ogilvyjbaskerville-bolditalic.woff
68 ms
ogilvyjbaskerville-regular.woff
69 ms
raleway-semibold.woff
67 ms
raleway-regular.woff
68 ms
photo_rafael-rosi.png
67 ms
about-loader.gif
67 ms
title_map-ogilvy-mather.png
65 ms
bg_arrow-empresas-list.png
65 ms
title_map-ogilvy-public.png
66 ms
title_map-ogilvy-one.png
67 ms
title_map-ogilvy-common.png
65 ms
title_map-ogilvy-neo.png
61 ms
sprite_close-video.png
62 ms
lion.png
63 ms
home-cases-text.png
64 ms
bg_container-error-contato.png
62 ms
bg_container-confirm-contato.png
60 ms
bg_title-vagas.png
60 ms
mapa-ogilvyone.jpg
62 ms
bg_icon-info-maps.png
60 ms
mapa-neoogilvy.jpg
59 ms
mapa-ogilvymather-rio.jpg
60 ms
mapa-ogilvymather-brasilia.jpg
60 ms
img-erro404.png
60 ms
5_capa.jpg
68 ms
4_capa.jpg
66 ms
3_capa.jpg
70 ms
2_capa.jpg
34 ms
analytics.js
51 ms
raleway-thin.woff
49 ms
collect
30 ms
collect
65 ms
135 ms
xd_arbiter.php
212 ms
xd_arbiter.php
419 ms
ping
57 ms
12799176_10154083923092994_4548764269254101275_n.jpg
486 ms
1800385_965404823528690_8836258220305418549_n.jpg
576 ms
12802705_964664946936011_888003415539693020_n.jpg
775 ms
12734182_999958220050710_3642010874359068482_n.jpg
711 ms
1914963_964130963656076_5353643470487282737_n.jpg
776 ms
1233438_963957977006708_3215701888240417282_n.jpg
776 ms
12814786_10154091266402994_5453945166339181657_n.jpg
979 ms
12803192_961682753900897_2017241969168050471_n.jpg
710 ms
12719973_961646807237825_1703325429_n.jpg
844 ms
12794541_10154101364697994_4287955649541662940_n.jpg
845 ms
1545806_960105144058658_5514213118817598658_n.jpg
844 ms
12804835_960022850733554_7518430619819366460_n.jpg
912 ms
12799090_959558287446677_9128253732661896717_n.jpg
1060 ms
12809663_1148347868532683_1850764204647454127_n.jpg
909 ms
12809562_957585807643925_805305609345396604_n.jpg
976 ms
bg_play-button.png
33 ms
ogilvy.com.br accessibility score
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.
ogilvy.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
ogilvy.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ogilvy.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ogilvy.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.
ogilvy.com.br
Open Graph data is detected on the main page of Ogilvy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: