Tools & Wizards About Us
webcompany.com.br screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

webcompany.com.br

Webcompany Marketing Digital - SEO, Inbound Marketing e Google Ads

Page Load Speed

2 sec in total

First Response

143 ms

Resources Loaded

1.4 sec

Page Rendered

469 ms

webcompany.com.br screenshot

About Website

Visit webcompany.com.br now to see the best up-to-date Webcompany content for Brazil and also check out these interesting facts you probably never knew about webcompany.com.br

A Webcompany é uma agência de marketing digital há 25 anos especializada em inbound marketing, SEO, Google Ads e redes sociais. Conheça!

Visit webcompany.com.br

Key Findings

We analyzed Webcompany.com.br page load time and found that the first response time was 143 ms and then it took 1.9 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.

Performance Metrics

webcompany.com.br performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

webcompany.com.br

143 ms

webcompany.com.br

134 ms

style.css

44 ms

style.min.css

43 ms

theme.min.css

51 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 80% of them (47 requests) were addressed to the original Webcompany.com.br, 7% (4 requests) were made to Googletagmanager.com and 3% (2 requests) were made to D335luupugsy2.cloudfront.net. The less responsive or slowest element that took the longest time to load (593 ms) relates to the external source D335luupugsy2.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.2 kB (47%)

Content Size

544.2 kB

After Optimization

288.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webcompany.com.br main page is 544.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. 70% of websites need less resources to load. HTML takes 297.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 255.5 kB

  • Original 297.5 kB
  • After minification 297.5 kB
  • After compression 42.0 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 255.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 36.0 kB
  • After minification 36.0 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. Webcompany images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 361 B

  • Original 175.0 kB
  • After minification 175.0 kB
  • After compression 174.6 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.

CSS Optimization

-1%

Potential reduce by 389 B

  • Original 35.7 kB
  • After minification 35.7 kB
  • After compression 35.4 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. Webcompany.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (88%)

Requests Now

48

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webcompany. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

webcompany.com.br

webcompany.com.br

143 ms

webcompany.com.br

webcompany.com.br

134 ms

style.css

style.css

44 ms

style.min.css

style.min.css

43 ms

theme.min.css

theme.min.css

51 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

44 ms

swiper.min.css

swiper.min.css

42 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

53 ms

she-header-style.css

she-header-style.css

58 ms

jquery.min.js

jquery.min.js

51 ms

jquery-migrate.min.js

jquery-migrate.min.js

53 ms

she-header.js

she-header.js

104 ms

js

js

99 ms

js

js

339 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

55 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

70 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

70 ms

custom-pro-widget-call-to-action.min.css

custom-pro-widget-call-to-action.min.css

82 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

82 ms

animations.min.css

animations.min.css

60 ms

lazysizes.min.js

lazysizes.min.js

69 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

71 ms

script.js

script.js

73 ms

hello-frontend.min.js

hello-frontend.min.js

82 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

90 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

196 ms

webpack.runtime.min.js

webpack.runtime.min.js

88 ms

frontend-modules.min.js

frontend-modules.min.js

195 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

198 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

199 ms

wp-polyfill.min.js

wp-polyfill.min.js

261 ms

hooks.min.js

hooks.min.js

325 ms

i18n.min.js

i18n.min.js

262 ms

frontend.min.js

frontend.min.js

325 ms

waypoints.min.js

waypoints.min.js

325 ms

core.min.js

core.min.js

325 ms

frontend.min.js

frontend.min.js

326 ms

elements-handlers.min.js

elements-handlers.min.js

327 ms

jquery.sticky.min.js

jquery.sticky.min.js

389 ms

8bca9318-fdca-4053-bfea-dff891a789c7-loader.js

8bca9318-fdca-4053-bfea-dff891a789c7-loader.js

542 ms

vef91dfe02fce4ee0ad053f6de4f175db1715022073587

vef91dfe02fce4ee0ad053f6de4f175db1715022073587

76 ms

fbevents.js

fbevents.js

235 ms

gtm.js

gtm.js

318 ms

banner_25.jpg

banner_25.jpg

237 ms

js

js

150 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf

151 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf

151 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjQ.ttf

209 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjQ.ttf

151 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf

150 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf

151 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjQ.ttf

210 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjQ.ttf

239 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjQ.ttf

211 ms

analytics.js

analytics.js

76 ms

collect

collect

35 ms

bundle.js

bundle.js

593 ms

collect

collect

32 ms

ga-audiences

ga-audiences

86 ms

Accessibility Review

webcompany.com.br accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

webcompany.com.br best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

webcompany.com.br SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webcompany.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 Webcompany.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.

Social Sharing Optimization

webcompany.com.br

Open Graph data is detected on the main page of Webcompany. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: