2.6 sec in total
412 ms
1.5 sec
693 ms
Visit webcore.com.br now to see the best up-to-date Webcore content and also check out these interesting facts you probably never knew about webcore.com.br
Webcore Interactive brings digital experiences to life through art, design and technology.
Visit webcore.com.brWe analyzed Webcore.com.br page load time and found that the first response time was 412 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
webcore.com.br performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value5.9 s
14/100
25%
Value7.1 s
30/100
10%
Value4,040 ms
1/100
30%
Value0.132
81/100
15%
Value14.6 s
8/100
10%
412 ms
73 ms
50 ms
95 ms
162 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Webcore.com.br, 80% (44 requests) were made to Webcore.digital and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (459 ms) relates to the external source Webcore.digital.
Page size can be reduced by 85.3 kB (19%)
437.3 kB
352.1 kB
In fact, the total size of Webcore.com.br main page is 437.3 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. Javascripts take 319.7 kB which makes up the majority of the site volume.
Potential reduce by 52.8 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 52.8 kB or 80% of the original size.
Potential reduce by 32.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 129 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. Webcore.com.br has all CSS files already compressed.
Number of requests can be reduced by 43 (90%)
48
5
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webcore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
webcore.com.br
412 ms
www.webcore.com.br
73 ms
webcore.digital
50 ms
95 ms
9427464.css
162 ms
4fc6808.css
121 ms
e0a0aa5.css
138 ms
a2c12f2.css
84 ms
59f2670.css
157 ms
d372d9b.css
158 ms
5c56f36.css
199 ms
5e8b542.css
186 ms
0007165.css
278 ms
email-decode.min.js
172 ms
state.js
239 ms
6275caa.js
243 ms
62d6c6d.js
258 ms
447515a.js
235 ms
f5c286c.js
268 ms
be297a1.js
351 ms
1e68a19.js
350 ms
d4241e8.js
352 ms
49bbacc.js
351 ms
ba9d622.js
360 ms
c2d1935.js
351 ms
e61bccb.js
459 ms
1b15176.js
420 ms
69c4baf.js
395 ms
rocket-loader.min.js
351 ms
vef91dfe02fce4ee0ad053f6de4f175db1715022073587
99 ms
normal.woff2
121 ms
normal.woff2
163 ms
normal.woff2
111 ms
gtm.js
84 ms
state.js
104 ms
6275caa.js
59 ms
62d6c6d.js
102 ms
447515a.js
34 ms
f5c286c.js
42 ms
be297a1.js
73 ms
1e68a19.js
45 ms
d4241e8.js
103 ms
49bbacc.js
102 ms
ba9d622.js
101 ms
c2d1935.js
127 ms
e61bccb.js
125 ms
1b15176.js
268 ms
69c4baf.js
135 ms
js
75 ms
analytics.js
18 ms
hotjar-2306126.js
148 ms
collect
12 ms
collect
104 ms
ga-audiences
83 ms
modules.7b6d7646601d8cd7fb5f.js
14 ms
webcore.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
webcore.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
webcore.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
![]()
EN
![]()
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webcore.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Webcore.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.
webcore.com.br
Open Graph data is detected on the main page of Webcore. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: