3.5 sec in total
515 ms
2.7 sec
212 ms
Click here to check amazing Opalhares content. Otherwise, check out these important facts you probably never knew about opalhares.com.br
Portfólio do designer gráfico e ilustrador Guilherme Palhares. Branding, Design Gráfico, Ilustração e Criação de Conteúdo.
Visit opalhares.com.brWe analyzed Opalhares.com.br page load time and found that the first response time was 515 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.
opalhares.com.br performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value9.3 s
1/100
25%
Value6.7 s
37/100
10%
Value320 ms
76/100
30%
Value1.166
1/100
15%
Value9.1 s
33/100
10%
515 ms
768 ms
63 ms
384 ms
255 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 43% of them (43 requests) were addressed to the original Opalhares.com.br, 49% (49 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Opalhares.com.br.
Page size can be reduced by 15.7 kB (3%)
574.2 kB
558.5 kB
In fact, the total size of Opalhares.com.br main page is 574.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 393.3 kB which makes up the majority of the site volume.
Potential reduce by 14.1 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 14.1 kB or 76% of the original size.
Potential reduce by 454 B
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. Opalhares images are well optimized though.
Potential reduce by 476 B
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 621 B
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. Opalhares.com.br has all CSS files already compressed.
Number of requests can be reduced by 20 (42%)
48
28
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Opalhares. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
opalhares.com.br
515 ms
www.opalhares.com.br
768 ms
js
63 ms
bootstrap.min.css
384 ms
font-awesome.min.css
255 ms
jquery.fancybox.css
275 ms
settings.css
268 ms
style.css
283 ms
theme.css
300 ms
default.css
387 ms
css
31 ms
jquery-1.10.1.min.js
584 ms
bootstrap.min.js
465 ms
dropdown-menu.js
465 ms
jquery.fancybox.pack.js
465 ms
jquery.fancybox-media.js
538 ms
jquery.themepunch.revolution.min.js
666 ms
jquery.isotope.min.js
609 ms
owl.carousel.min.js
611 ms
plugins.js
644 ms
theme.js
664 ms
site-logo.svg
761 ms
S-3_bg.jpg
820 ms
S-3_ilustra.png
856 ms
ballo-in-maschera.jpg
899 ms
guia-de-bolso-amove.png
896 ms
revista-casemodding.jpg
898 ms
no-entorno_1.png
813 ms
cerpm.jpg
963 ms
coopmil-em-revista.jpg
956 ms
coopmil-25-anos.jpg
1136 ms
fera.jpg
1021 ms
ilustra-amigos-da-terra.png
1025 ms
ilustra-dh.png
1042 ms
e-webmkt.png
1093 ms
video-interativo-amove.png
1108 ms
cheil.png
1162 ms
4net.png
1163 ms
brando.png
1203 ms
cerpm.png
1234 ms
js
64 ms
analytics.js
25 ms
collect
55 ms
coopmil.png
1003 ms
noentorno.png
1020 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
18 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
16 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
19 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
18 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
17 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
18 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
18 ms
KFOkCnqEu92Fr1MmgVxIIzQXKMny.woff
27 ms
KFOkCnqEu92Fr1MmgVxGIzQXKMnyrYk.woff
29 ms
KFOkCnqEu92Fr1MmgVxHIzQXKMnyrYk.woff
27 ms
KFOkCnqEu92Fr1MmgVxLIzQXKMnyrYk.woff
23 ms
KFOkCnqEu92Fr1MmgVxEIzQXKMnyrYk.woff
26 ms
KFOkCnqEu92Fr1MmgVxMIzQXKMnyrYk.woff
27 ms
KFOkCnqEu92Fr1MmgVxFIzQXKMnyrYk.woff
29 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
63 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
60 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
60 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
58 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
60 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
62 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
61 ms
KFOlCnqEu92Fr1MmEU9fBBc-AMP6lQ.woff
62 ms
KFOlCnqEu92Fr1MmEU9fChc-AMP6lbBP.woff
138 ms
KFOlCnqEu92Fr1MmEU9fCxc-AMP6lbBP.woff
134 ms
KFOlCnqEu92Fr1MmEU9fBxc-AMP6lbBP.woff
136 ms
KFOlCnqEu92Fr1MmEU9fCBc-AMP6lbBP.woff
63 ms
KFOlCnqEu92Fr1MmEU9fABc-AMP6lbBP.woff
137 ms
KFOlCnqEu92Fr1MmEU9fCRc-AMP6lbBP.woff
130 ms
KFOlCnqEu92Fr1MmWUlfBBc-AMP6lQ.woff
63 ms
KFOlCnqEu92Fr1MmWUlfChc-AMP6lbBP.woff
64 ms
KFOlCnqEu92Fr1MmWUlfCxc-AMP6lbBP.woff
64 ms
KFOlCnqEu92Fr1MmWUlfBxc-AMP6lbBP.woff
65 ms
KFOlCnqEu92Fr1MmWUlfCBc-AMP6lbBP.woff
65 ms
KFOlCnqEu92Fr1MmWUlfABc-AMP6lbBP.woff
107 ms
KFOlCnqEu92Fr1MmWUlfCRc-AMP6lbBP.woff
130 ms
KFOlCnqEu92Fr1MmYUtfBBc-AMP6lQ.woff
131 ms
fontawesome-webfont.woff
954 ms
KFOlCnqEu92Fr1MmYUtfChc-AMP6lbBP.woff
152 ms
KFOlCnqEu92Fr1MmYUtfCxc-AMP6lbBP.woff
153 ms
KFOlCnqEu92Fr1MmYUtfBxc-AMP6lbBP.woff
153 ms
KFOlCnqEu92Fr1MmYUtfCBc-AMP6lbBP.woff
121 ms
KFOlCnqEu92Fr1MmYUtfABc-AMP6lbBP.woff
156 ms
KFOlCnqEu92Fr1MmYUtfCRc-AMP6lbBP.woff
271 ms
KFOjCnqEu92Fr1Mu51TjASc6CsLYl4BO.woff
155 ms
KFOjCnqEu92Fr1Mu51TjASc0CsLYl4BOQ3o.woff
168 ms
KFOjCnqEu92Fr1Mu51TjASc1CsLYl4BOQ3o.woff
142 ms
KFOjCnqEu92Fr1Mu51TjASc5CsLYl4BOQ3o.woff
199 ms
KFOjCnqEu92Fr1Mu51TjASc2CsLYl4BOQ3o.woff
143 ms
KFOjCnqEu92Fr1Mu51TjASc-CsLYl4BOQ3o.woff
262 ms
KFOjCnqEu92Fr1Mu51TjASc3CsLYl4BOQ3o.woff
264 ms
analytics.js
42 ms
collect
65 ms
loader.gif
536 ms
timer.png
589 ms
opalhares.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
opalhares.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
opalhares.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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Opalhares.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 Opalhares.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.
opalhares.com.br
Open Graph data is detected on the main page of Opalhares. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: