Worldpc.Com.Br - Info receives about 907 unique visitors and 2,722 (3.00 per visitor) page views per day which should earn about $11.10/day from advertising revenue. Estimated site value is $8,106.46. According to Alexa Traffic Rank is ranked number 1,516,804 in the world and 2.0E-5% of global Internet users visit it. Site is hosted in Brazil and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Web Frameworks
Microsoft ASP.NET
Font Scripts
Google Font API
Tag Managers
Google Tag Manager
Web Servers
JavaScript Libraries
Operating Systems
Windows Server Profile

Title: WorldPC - O melhor da tecnologia aqui!
Description: Aqui é o lugar que você procura pra comprar suas peças de computador! Temos computadores All In One, Notebooks, Desktops!
Last update was 11 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

0.9K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
1,516,804 visit alexa
Alexa Reach:
2.0E-5%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:

Brazil, BR

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.9s 50% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 50% 35% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 35% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)15ms 96% of loads for this page have a fast (<100ms) First Input Delay (FID) 96% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.8s 57% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 57% 27% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 27% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)18ms 96% of loads for this page have a fast (<100ms) First Input Delay (FID) 96% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

Lab Data

First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 230 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 180 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.1 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 2,203 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

995 KB
184 KB
117 KB,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05
87 KB
81 KB
76 KB
45 KB
35 KB
33 KB
33 KB
Minimizes main-thread work - 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
Style & Layout
390 ms
Script Evaluation
377 ms
146 ms
71 ms
Parse HTML & CSS
57 ms
Script Parsing & Compilation
29 ms
Garbage Collection
5 ms
Serve images in next-gen formats - Potential savings of 75 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
44 KB26 KB
32 KB21 KB
30 KB20 KB
11 KB9 KB
Avoid an excessive DOM size - 994 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 86 requests • 2,203 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
862203 KB
41372 KB
51454 KB
18220 KB
4115 KB
239 KB
74 KB
00 KB
48441 KB
Eliminate render-blocking resources - Potential savings of 470 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
20 KB350
1 KB230
24 KB350
8 KB270
14 KB310,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05
87 KB470
33 KB390,fbits.componente.banner.js,fbits.componente.listaSpot.js,fbits.componente.listaMarcas.js,p/jquery.lazyload.min.js,fbits.framework.js,fbits.parceiro.js,fbits.cookie.js&v=20191109_05
14 KB310
Efficiently encode images - Potential savings of 66 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
44 KB25 KB
30 KB18 KB
15 KB9 KB
32 KB9 KB
11 KB5 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms129 ms0 KB0 KB301text/html
130 ms391 ms21 KB114 KB200text/htmlDocument
404 ms428 ms20 KB118 KB200text/cssStylesheet
404 ms424 ms1 KB2 KB200text/cssStylesheet
404 ms427 ms24 KB68 KB200application/javascriptScript
404 ms432 ms8 KB20 KB200application/javascriptScript
404 ms430 ms14 KB50 KB200text/javascriptScript,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05
405 ms964 ms87 KB508 KB200text/cssStylesheet
405 ms671 ms33 KB92 KB200text/javascriptScript,fbits.componente.banner.js,fbits.componente.listaSpot.js,fbits.componente.listaMarcas.js,p/jquery.lazyload.min.js,fbits.framework.js,fbits.parceiro.js,fbits.cookie.js&v=20191109_05
405 ms538 ms14 KB53 KB200text/javascriptScript
405 ms537 ms35 KB49 KB200image/svg+xmlImage
405 ms531 ms3 KB7 KB200image/svg+xmlImage
797 ms922 ms3 KB9 KB200image/svg+xmlImage,fbits.headerFloating.js&v=20191109_06
532 ms659 ms2 KB5 KB200text/javascriptScript
806 ms1365 ms9 KB8 KB200image/webpImage
923 ms1474 ms9 KB8 KB200image/webpImage
1013 ms1568 ms11 KB11 KB200image/webpImage
1014 ms1576 ms15 KB14 KB200image/webpImage
1014 ms1572 ms9 KB8 KB200image/webpImage
1014 ms1578 ms9 KB8 KB200image/webpImage
1014 ms1576 ms9 KB8 KB200image/webpImage
1014 ms1580 ms8 KB7 KB200image/webpImage
1014 ms1578 ms8 KB8 KB200image/webpImage
1015 ms1614 ms10 KB9 KB200image/webpImage
1015 ms1576 ms6 KB5 KB200image/webpImage
1015 ms1577 ms3 KB3 KB200image/webpImage
1015 ms1617 ms8 KB8 KB200image/webpImage
1015 ms1574 ms14 KB13 KB200image/webpImage
1015 ms1573 ms9 KB8 KB200image/webpImage
1015 ms1622 ms7 KB7 KB200image/webpImage
1016 ms1581 ms2 KB2 KB200image/webpImage
1016 ms1577 ms9 KB8 KB200image/webpImage
1016 ms1573 ms12 KB12 KB200image/webpImage
409 ms1064 ms0 KB0 KB-1Image
1017 ms1580 ms1 KB1 KB200image/webpImage
1017 ms1574 ms7 KB6 KB200image/webpImage
1017 ms1617 ms1 KB1 KB200image/webpImage
1017 ms1578 ms12 KB12 KB200image/webpImage
1017 ms1590 ms4 KB4 KB200image/webpImage
1017 ms1592 ms0 KB0 KB302text/html
1017 ms1591 ms0 KB0 KB302text/html
1018 ms1590 ms0 KB0 KB302text/html
1018 ms1591 ms0 KB0 KB302text/html
1018 ms1273 ms15 KB15 KB200image/jpegImage
1018 ms1508 ms17 KB17 KB200image/jpegImage
1018 ms1396 ms15 KB14 KB200image/jpegImage
1018 ms1392 ms31 KB30 KB200image/jpegImage
410 ms1064 ms0 KB0 KB-1Script
1019 ms1166 ms3 KB11 KB200image/svg+xmlImage
1019 ms1635 ms45 KB44 KB200image/jpegImage
1019 ms1271 ms33 KB32 KB200image/jpegImage
410 ms1064 ms0 KB0 KB-1Image
1019 ms1385 ms7 KB7 KB200image/jpegImage
1019 ms1157 ms5 KB5 KB200image/jpegImage
1020 ms1154 ms3 KB3 KB200image/jpegImage
411 ms1065 ms0 KB0 KB-1Image
540 ms671 ms1 KB1 KB200text/javascriptScript,jquery.touchwipe.1.1.1.js,fbits.carrinho.cabecalho.js,fbits.share.js,jquery.autocomplete.js,fbitsSearch.config.js,fbitsSearch.js,barraProdutosVistos.js,jquery.fancybox-1.3.4.js,jquery.validate.min.js,fbits.produto.avise-me.js,fbits.listadedesejos.js,jquery.slides.min.js,main.js,fbits.googleanalytics.js,formatNumber.js,jquery.exitintent.js,p/jquery.elevateZoom-3.0.8.min.js,fbits.produto.atributos.js,fbits.produto.newFunctions.js&v=20191109_06
411 ms1065 ms0 KB0 KB-1Script
411 ms1065 ms0 KB0 KB-1Script
660 ms805 ms1 KB0 KB200text/htmlScript
672 ms796 ms1 KB5 KB200text/javascriptScript
1012 ms1145 ms1 KB0 KB200application/jsonXHR
1019 ms1065 ms0 KB0 KB-1Script
1031 ms1065 ms0 KB0 KB-1Image
1033 ms1165 ms11 KB11 KB200image/jpegImage
1036 ms1527 ms117 KB117 KB200application/x-font-woffFont
1036 ms1671 ms995 KB995 KB200application/octet-streamFont
1037 ms2063 ms184 KB184 KB200application/octet-streamFont
1037 ms1165 ms76 KB75 KB200application/font-woff2Font
1101 ms1161 ms17 KB58 KB200text/htmlDocument
1147 ms1605 ms1 KB1 KB404text/htmlImage
1575 ms2126 ms7 KB6 KB200image/webpImage
1591 ms2152 ms2 KB2 KB200image/pngImage
1591 ms2152 ms4 KB4 KB200image/pngImage
1591 ms2143 ms2 KB1 KB200image/pngImage
1593 ms2144 ms4 KB3 KB200image/pngImage,cross/R_nNu6ob2q7.css?_nc_x=Ij3Wp8lg5Kz
1658 ms1677 ms8 KB32 KB200text/cssStylesheet
1659 ms1698 ms81 KB312 KB200application/x-javascriptScript
1659 ms1696 ms25 KB87 KB200application/x-javascriptScript
1659 ms1691 ms8 KB24 KB200application/x-javascriptScript
1659 ms1683 ms5 KB14 KB200application/x-javascriptScript
1659 ms1678 ms11 KB11 KB200image/jpegImage
1659 ms1678 ms2 KB1 KB200image/jpegImage
1845 ms1860 ms2 KB1 KB200image/pngImage
1872 ms1891 ms3 KB8 KB200application/x-javascriptScript
2908 ms2944 ms1 KB0 KB200text/htmlXHR
Serve static assets with an efficient cache policy - 27 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
764000 ms1 KB
604800000 ms995 KB
604800000 ms184 KB
604800000 ms117 KB
604800000 ms76 KB
604800000 ms45 KB
604800000 ms35 KB
604800000 ms33 KB
604800000 ms31 KB
604800000 ms17 KB
604800000 ms15 KB
604800000 ms15 KB
604800000 ms11 KB
604800000 ms7 KB
604800000 ms5 KB
604800000 ms3 KB
604800000 ms3 KB
604800000 ms3 KB
604800000 ms3 KB,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05
1209600000 ms87 KB
1209600000 ms33 KB,fbits.componente.banner.js,fbits.componente.listaSpot.js,fbits.componente.listaMarcas.js,p/jquery.lazyload.min.js,fbits.framework.js,fbits.parceiro.js,fbits.cookie.js&v=20191109_05
1209600000 ms14 KB
1209600000 ms11 KB,fbits.headerFloating.js&v=20191109_06
1209600000 ms2 KB
1209600000 ms2 KB
1209600000 ms1 KB
1209600000 ms1 KB
Minimize third-party usage - Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

SizeMain-Thread Blocking Time
164 KB0 ms
34 KB0 ms
24 KB0 ms
8 KB0 ms
0 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
412 ms
7 ms
423 ms
5 ms
448 ms
9 ms
458 ms
14 ms
476 ms
6 ms
551 ms
8 ms
559 ms
6 ms
942 ms
6 ms
986 ms
22 ms
1014 ms
11 ms
1027 ms
14 ms
1042 ms
34 ms
1076 ms
7 ms
1086 ms
28 ms
1124 ms
11 ms
1137 ms
6 ms
1143 ms
452 ms
1595 ms
12 ms
1612 ms
6 ms
1643 ms
13 ms
1656 ms
8 ms
1665 ms
6 ms
1683 ms
59 ms
1754 ms
8 ms
1768 ms
47 ms
1815 ms
16 ms
1842 ms
20 ms
1862 ms
30 ms
1915 ms
5 ms
2086 ms
50 ms
2154 ms
5 ms
2168 ms
6 ms
2175 ms
8 ms
2919 ms
8 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
491 ms
635 ms
1027 ms
127 ms
JavaScript execution time - 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
475 ms9 ms2 ms
468 ms270 ms2 ms
Defer offscreen images - Potential savings of 11 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
8 KB8 KB
3 KB3 KB
Properly size images - Potential savings of 184 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
44 KB41 KB
32 KB32 KB
30 KB28 KB
17 KB15 KB
14 KB13 KB
15 KB13 KB
7 KB5 KB
14 KB5 KB
13 KB4 KB
12 KB4 KB
9 KB3 KB
8 KB3 KB
8 KB3 KB
8 KB3 KB
7 KB3 KB
7 KB2 KB
5 KB2 KB
6 KB2 KB
6 KB2 KB
Remove unused CSS - Potential savings of 97 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05
87 KB78 KB
20 KB19 KB
Avoid chaining critical requests - 16 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 260 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Page Speed (Google PageSpeed Insights) - Mobile

Currently Not Available

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:,fbits.componente.banner.js,fbits.componente.listaSpot.js,fbits.componente.listaMarcas.js,p/jquery.lazyload.min.js,fbits.framework.js,fbits.parceiro.js,fbits.cookie.js&v=20191109_05
Optimize CSS Delivery of the following:,slick.css,slick-theme.css,style.novo.css,responsive-tablet.novo.css,responsive-desktop.novo.css,styles.css,responsive-tablet.css,responsive-desktop.css,header.css,spot.css,footer.css,fancybox.css,autocomplete/default.css,autocomplete/custom.css&v=20191109_05

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 149.8KiB (81% reduction).

Compressing and resizing could save 38.6KiB (87% reduction).
Compressing and resizing could save 31.6KiB (97% reduction).
Compressing and resizing could save 28KiB (91% reduction).
Compressing and resizing could save 15.1KiB (88% reduction).
Compressing and resizing could save 13.5KiB (90% reduction).
Compressing and resizing could save 12.7KiB (87% reduction).
Compressing and resizing could save 6.6KiB (87% reduction).
Compressing could save 1,011B (14% reduction).
Compressing could save 637B (14% reduction).
Compressing https://static.*** could save 518B (37% reduction).
Compressing https://scontent-ort2-2.******802335_784471955324097_5741748001982906368_n.jpg?_nc_cat=110&_nc_oc=AQnF2DaxnKnfRio5ypPkpyhMqflqL6HSD_J_8UkBToqVV0mxbD87drhy7W7idEMatrA&_nc_ht=scontent-ort2-2.***&oh=8b013ded5ffab2898c9a8ee8c6c9b72a&oe=5E50C918 could save 430B (35% reduction).
Compressing could save 362B (12% reduction).
Compressing could save 330B (21% reduction).
Compressing could save 317B (11% reduction).
Compressing could save 188B (13% reduction).

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 418 CSS pixels wide, but the viewport is only 403 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="" class="headerLogo"></a> falls outside the viewport.
The element <div class="col-4">Minha Conta…Carrinho Vazio</div> falls outside the viewport.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <button id="btnBuscaMobile" type="button" class="btSearch greenBack">buscar</button> is close to 1 other tap targets .
The tap target <button type="button" class="slick-prev slick-arrow">Previous</button> and 3 others are close to other tap targets .
The tap target <button type="button" class="slick-prev slick-arrow">Previous</button> and 3 others are close to other tap targets .
The tap target <a href="https://www.wo…">Quem Somos</a> and 7 others are close to other tap targets.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (15 minutes)*** (2 hours)

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 3KiB (20% reduction).

Minifying could save 3KiB (20% reduction) after compression.

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 144B (31% reduction).

Compressing could save 144B (31% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 113.62 KB
Compressed size: 20.73 KB
File reduced by: 92.89 KB (81%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *
Issuer: AlphaSSL CA - SHA256 - G2
Valid from: Apr 23 17:37:44 2019 GMT
Valid until: Apr 23 17:37:44 2020 GMT

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Type: text/html; charset=UTF-8
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
Date: Sat, 09 Nov 2019 09:31:04 GMT
Content-Length: 150

HTTP/1.1 200 OK
Cache-Control: public, max-age=689
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Expires: Sat, 09 Nov 2019 09:42:34 GMT
Last-Modified: Sat, 09 Nov 2019 09:12:34 GMT
Vary: User-Agent,Accept-Encoding
Server: Microsoft-IIS/8.5
X-AspNetMvc-Version: 5.2
x-PoweredBy: FBITS -
x-TempoPesquisa: 00:00:00.0156314
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Content-Type
Access-Control-Allow-Methods: POST, GET, OPTIONS
Date: Sat, 09 Nov 2019 09:31:04 GMT
Content-Length: 21230

+ DNS Lookup

Type Ip Target TTL
MX 900
TXT 900
SOA 900
Serial Number 2019080102
Refresh 7200
Retry 600
Expire 1728000
Minimum TTL 0
A 862
NS 900
NS 900

+ Whois Lookup

Domain Created:
Domain Age:

whois lookup at
% Copyright (c)
% The use of the data below is only permitted as described in
% full by the terms of use at ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2019-11-09T06:31:41-03:00

owner: Bel Micro Com***dores Ltda Eireli
owner-c: GDEMA
admin-c: GDEMA
tech-c: FDSSA11
billing-c: GDEMA
nsstat: 20191108 AA
nslastaa: 20191108
nsstat: 20191108 AA
nslastaa: 20191108
saci: yes
created: 20180709 #18549655
changed: 20190422
expires: 20200709
status: published

nic-hdl-br: GDEMA
person: Gustavo Demetrius Esteves Martins
created: 20130218
changed: 20191010

nic-hdl-br: FDSSA11
created: 20130220
changed: 20191001

% Security and mail abuse issues should also be addressed to
%, , respectivelly to email
% and email
% accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, contact handle (ID), CIDR block, IP and ASN.
Last update was 11 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
1 secs
8 secs
25 secs
35 secs
1 min
1 min
1 min
2 mins
2 mins
2 mins

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget