4.2 sec in total
567 ms
3 sec
645 ms
Welcome to omago.com.br homepage info - get ready to check Omago best content right away, or after learning these important things about omago.com.br
Mágico Kronnus - O Ilusionista do Fantástico. Show de Mágica e Ilusionismo com um dos mágicos de maior expressão do Brasil. Eventos corporativos, palestras, shows e ilusionismos personalizados.
Visit omago.com.brWe analyzed Omago.com.br page load time and found that the first response time was 567 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
omago.com.br performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value22.5 s
0/100
25%
Value27.6 s
0/100
10%
Value14,360 ms
0/100
30%
Value0.022
100/100
15%
Value30.4 s
0/100
10%
567 ms
164 ms
25 ms
36 ms
45 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 21% of them (30 requests) were addressed to the original Omago.com.br, 25% (35 requests) were made to Static.xx.fbcdn.net and 9% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Omago.com.br.
Page size can be reduced by 1.1 MB (30%)
3.7 MB
2.6 MB
In fact, the total size of Omago.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. 85% 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 19.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.3 kB or 74% of the original size.
Potential reduce by 156.3 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. Omago images are well optimized though.
Potential reduce by 713.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 713.4 kB or 68% of the original size.
Potential reduce by 235.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. Omago.com.br needs all CSS files to be minified and compressed as it can save up to 235.6 kB or 83% of the original size.
Number of requests can be reduced by 74 (55%)
134
60
The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omago. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
omago.com.br
567 ms
style.css
164 ms
css
25 ms
css
36 ms
css
45 ms
lightbox.css
275 ms
jquery-1.8.2.min.js
435 ms
jquery.easing.1.3.js
290 ms
jquery.animate-colors-min.js
301 ms
jquery.zlayer.min.js
293 ms
funcoes.js
309 ms
drop.css
419 ms
jquery-ui-1.8.18.custom.min.js
432 ms
jquery.smooth-scroll.min.js
502 ms
lightbox.js
502 ms
css
55 ms
desenvolvimento_white.png
408 ms
back2.jpg
781 ms
temp2.jpg
575 ms
logo.png
172 ms
temp.jpg
1498 ms
omagop.png
1275 ms
twitter.png
183 ms
youtube.png
405 ms
facebook.png
409 ms
back_sub_menu.png
485 ms
Show_Kronnus_2453.jpg
1469 ms
Depoimentos_1498.jpg
653 ms
Depoimentos_6605.jpg
779 ms
up.png
830 ms
enviar.png
1166 ms
widgets.js
12 ms
uEqZRaXFzp8
97 ms
embed
277 ms
back_natal.jpg
1310 ms
back_fale.jpg
1730 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
30 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
74 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
98 ms
sdk.js
108 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
47 ms
loading.gif
1246 ms
close.png
1369 ms
www-embed-player-vflfNyN_r.css
60 ms
www-embed-player.js
141 ms
base.js
197 ms
likebox.php
504 ms
syndication
319 ms
349993120223592448
398 ms
271 ms
xd_arbiter.php
164 ms
xd_arbiter.php
270 ms
js
177 ms
init_embed.js
170 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
29 ms
ad_status.js
81 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
70 ms
ebiMDO3r-8l.css
277 ms
jGc-59L_9lo.css
306 ms
6qHpHChjY_J.css
344 ms
ztINr5qMqM_.css
525 ms
uVjHKJ0glvg.css
489 ms
ZY-3seVVf0G.css
510 ms
W9IvqTWpWa9.css
455 ms
q68gy-v_YMF.js
537 ms
FJmpeSpHpjS.js
573 ms
0wM5s1Khldu.js
560 ms
1bNoFZUdlYZ.js
563 ms
njO1TPvGzoR.js
560 ms
1QuX41zDRrx.js
564 ms
Oagsvfb4VWi.js
563 ms
LTv6ZK-5zxz.js
623 ms
1FCa-btixu2.js
567 ms
IjqSyiwKeaX.js
568 ms
rBxSIHk4zIe.js
613 ms
n6VgtouijQL.js
568 ms
7BE0CZr3HTs.js
610 ms
pQrUxxo5oQp.js
618 ms
_UYztdBNTjs.js
613 ms
-7JBD_ybv4q.js
717 ms
Kt4tkgSRvHH.js
618 ms
-etRC7LeCnhkSo2Y.jpg
430 ms
common.js
73 ms
map.js
95 ms
google4.png
153 ms
overlay.js
138 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
41 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
42 ms
util.js
153 ms
onion.js
150 ms
search_impl.js
147 ms
stats.js
95 ms
2d675bcc968901c49350a318cad63d4d_normal.png
324 ms
1D03kmh1_normal.jpg
402 ms
y9y0pnyfiaz4ygnf3km5_normal.jpeg
316 ms
LMkq4FtH_normal.jpg
315 ms
p1PFZixs_normal.jpg
315 ms
CX-aS_CWMAAIsC5.png:large
620 ms
COJKR_2UkAEjYuB.jpg
454 ms
openhand_8_8.cur
104 ms
ViewportInfoService.GetViewportInfo
158 ms
ViewportInfoService.GetViewportInfo
127 ms
kh
257 ms
transparent.png
65 ms
controls.js
49 ms
ViewportInfoService.GetViewportInfo
151 ms
css
118 ms
entity11.png
117 ms
mapcnt6.png
67 ms
vt
278 ms
vt
280 ms
vt
261 ms
vt
185 ms
vt
181 ms
vt
183 ms
vt
280 ms
vt
277 ms
vt
279 ms
tmapctrl.png
43 ms
jot
147 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
142 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
141 ms
10612793_738379876211885_3247458982716301335_n.jpg
361 ms
safe_image.php
200 ms
946176_955033234546547_7638040206283484957_n.jpg
369 ms
12720108_948698111845806_789380744_n.jpg
448 ms
940894_989354734447730_5139877287599940237_n.jpg
449 ms
1914550_1697371337214639_8016835565661757703_n.jpg
589 ms
12650891_964604003589470_6099221580129334420_n.png
559 ms
wL6VQj7Ab77.png
133 ms
s7jcwEQH7Sx.png
132 ms
l5aPruN9xMM.png
133 ms
pimRBh7B6ER.png
134 ms
QDwYpIaRyfG.png
132 ms
Qs-Ha2XZpNj.png
131 ms
sSwLTfB7PfP.png
143 ms
K00K-UgnsKu.png
141 ms
b8XhdWI9eAN.js
65 ms
K_65vAc89SX.png
50 ms
AuthenticationService.Authenticate
40 ms
I6-MnjEovm5.js
21 ms
omago.com.br accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
omago.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
omago.com.br SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omago.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Omago.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.
omago.com.br
Open Graph description is not detected on the main page of Omago. 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: