Airfox.Com.Br - Info receives about 136 unique visitors and 271 (2.00 per visitor) page views per day which should earn about $0.40/day from advertising revenue. Estimated site value is $162.56. According to Alexa Traffic Rank is ranked number 3,490,762 in the world and 8.0E-6% of global Internet users visit it. Site is hosted in Mountain View, California, 94043, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Technologies used on Website

Google Analytics
Font Scripts
Google Font API
Tag Managers
Google Tag Manager
Netlify Profile

Title: Bad Request
Description: Airfox is transforming the quality and availability of financial services in emerging markets. Offering centralized personal finance management and transparent, no-cost solutions, Airfox is changing the way people manage their money.
Last update was 305 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

136 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
3,490,762 visit alexa
Alexa Reach:
8.0E-6%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Brazil 86.6%82.4%80371

Where do visitors go on this site?


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

Brazil 223$0.40

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

BlockedLost Money
Brazil 13$0.02

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Google LLC 
Server Location:
Mountain View
California, CA
United States, US

Other sites hosted on

+ How fast does load?

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

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Max Potential First Input Delay 90 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.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 3690 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.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.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
470 ms
8 ms
480 ms
30 ms
634 ms
40 ms
690 ms
45 ms
763 ms
15 ms
784 ms
12 ms
797 ms
10 ms
813 ms
10 ms
830 ms
10 ms
853 ms
12 ms
870 ms
11 ms
886 ms
12 ms
901 ms
14 ms
915 ms
12 ms
931 ms
10 ms
956 ms
13 ms
970 ms
10 ms
982 ms
10 ms
997 ms
9 ms
1013 ms
11 ms
1030 ms
9 ms
1269 ms
6 ms
1330 ms
14 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
687 ms
685 ms
JavaScript execution time - 0.2 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
1733 ms21 ms6 ms
171 ms137 ms1 ms
72 ms70 ms1 ms
Defer offscreen images - Potential savings of 1,327 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
796 KB796 KB
274 KB274 KB
182 KB182 KB
28 KB28 KB
11 KB11 KB
9 KB9 KB
7 KB7 KB
7 KB7 KB
6 KB6 KB
4 KB4 KB
4 KB4 KB
Properly size images - Potential savings of 1,061 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
796 KB488 KB
423 KB257 KB
243 KB120 KB
182 KB108 KB
16 KB15 KB
12 KB11 KB
10 KB9 KB
28 KB8 KB
21 KB6 KB
20 KB6 KB
20 KB5 KB
18 KB5 KB
5 KB4 KB
16 KB4 KB
13 KB3 KB
11 KB3 KB
11 KB3 KB
9 KB3 KB
9 KB2 KB
Avoids enormous network payloads - Total size was 2,421 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

796 KB
424 KB
275 KB
243 KB
182 KB
159 KB
28 KB
21 KB
21 KB
20 KB
Minimizes main-thread work - 2.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Style & Layout
706 ms
533 ms
405 ms
Script Evaluation
239 ms
Parse HTML & CSS
95 ms
Script Parsing & Compilation
14 ms
Serve images in next-gen formats - Potential savings of 1,423 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
796 KB602 KB
423 KB328 KB
274 KB146 KB
182 KB109 KB
158 KB82 KB
243 KB73 KB
28 KB14 KB
20 KB11 KB
21 KB11 KB
18 KB10 KB
20 KB10 KB
16 KB9 KB
13 KB9 KB
16 KB8 KB
Avoids an excessive DOM size - 177 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can 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 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

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

Resource Type
RequestsTransfer Size
522421 KB
422363 KB
228 KB
219 KB
15 KB
25 KB
32 KB
00 KB
462010 KB
Eliminate render-blocking resources - Potential savings of 780 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,400,500,700
1 KB780
3 KB780
Efficiently encode images - Potential savings of 51 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
274 KB51 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms371 ms0 KB0 KB301text/plain
372 ms447 ms5 KB14 KB200text/htmlDocument
460 ms495 ms18 KB43 KB200text/javascriptScript,400,500,700
460 ms508 ms1 KB7 KB200text/cssStylesheet
461 ms603 ms3 KB14 KB200text/cssStylesheet
461 ms603 ms6 KB16 KB200image/svg+xmlImage
466 ms604 ms4 KB8 KB200image/svg+xmlImage
466 ms609 ms1 KB2 KB200image/svg+xmlImage
466 ms609 ms1 KB2 KB200image/svg+xmlImage
466 ms609 ms2 KB3 KB200image/svg+xmlImage
467 ms672 ms2 KB3 KB200image/svg+xmlImage
467 ms681 ms1 KB2 KB200image/svg+xmlImage
467 ms682 ms2 KB5 KB200image/svg+xmlImage
467 ms682 ms4 KB8 KB200image/svg+xmlImage
467 ms691 ms6 KB13 KB200image/svg+xmlImage
467 ms692 ms7 KB22 KB200image/svg+xmlImage
468 ms692 ms2 KB4 KB200image/svg+xmlImage
468 ms822 ms796 KB796 KB200image/pngImage
468 ms823 ms4 KB10 KB200image/svg+xmlImage
468 ms824 ms182 KB182 KB200image/jpegImage
469 ms825 ms7 KB16 KB200image/svg+xmlImage
469 ms825 ms275 KB274 KB200image/jpegImage
469 ms826 ms28 KB28 KB200image/pngImage
469 ms826 ms12 KB11 KB200image/pngImage
469 ms826 ms10 KB9 KB200image/pngImage
469 ms827 ms9 KB9 KB200image/pngImage
470 ms848 ms20 KB20 KB200image/pngImage
470 ms848 ms13 KB13 KB200image/pngImage
470 ms849 ms11 KB11 KB200image/pngImage
470 ms849 ms16 KB16 KB200image/pngImage
470 ms849 ms19 KB18 KB200image/pngImage
470 ms906 ms21 KB20 KB200image/pngImage
470 ms908 ms21 KB21 KB200image/pngImage
470 ms909 ms424 KB423 KB200image/pngImage
470 ms910 ms1 KB1 KB200image/svg+xmlImage
471 ms911 ms2 KB2 KB200image/svg+xmlImage
471 ms911 ms1 KB1 KB200image/svg+xmlImage
471 ms911 ms1 KB2 KB200image/svg+xmlImage
471 ms912 ms5 KB5 KB200image/pngImage
471 ms912 ms12 KB12 KB200image/pngImage
471 ms912 ms16 KB16 KB200image/pngImage
471 ms961 ms10 KB10 KB200image/pngImage
466 ms604 ms2 KB4 KB200application/javascriptScript
482 ms1231 ms159 KB158 KB200image/jpegImage
482 ms1247 ms3 KB14 KB200image/svg+xmlImage
483 ms1302 ms243 KB243 KB200image/jpegImage
616 ms1303 ms14 KB13 KB200font/woff2Font
618 ms1303 ms14 KB13 KB200font/woff2Font
623 ms1360 ms1 KB1 KB200image/svg+xmlImage
712 ms1364 ms1 KB0 KB302text/html
1364 ms1371 ms1 KB0 KB302text/html
1371 ms1382 ms1 KB0 KB200image/gifImage
Uses efficient cache policy on static assets - 1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
7200000 ms18 KB
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.

Remove unused CSS
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.

Minimize Critical Requests Depth - 5 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 80 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

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

Optimize the following images to reduce their size by 418.8KiB (23% reduction).

Compressing could save 156.3KiB (20% reduction).
Compressing could save 99.1KiB (37% reduction).
Compressing could save 32.6KiB (14% reduction).
Compressing could save 31.9KiB (21% reduction).
Compressing could save 18.9KiB (11% reduction).
Compressing and resizing***9e76/f07e1/images/uploads/mitunder35-1-.png could save 15KiB (94% reduction).
Compressing and resizing could save 10.9KiB (93% reduction).
Compressing and resizing could save 9.1KiB (94% reduction).
Compressing could save 6.7KiB (33% reduction).
Compressing could save 6.4KiB (32% reduction).
Compressing could save 5.4KiB (28% reduction).
Compressing***e61460a14f42130551d2dda439b7d8/52e79/images/uploads/logo-sherlock-2x.png could save 5KiB (28% reduction).
Compressing***31/c6536/images/uploads/logo-viavarejo-2x.png could save 4.9KiB (18% reduction).
Compressing and resizing could save 4.1KiB (90% reduction).
Compressing could save 4KiB (32% reduction).
Compressing could save 2.5KiB (27% reduction).
Compressing could save 2.2KiB (26% reduction).
Compressing could save 2.1KiB (19% reduction).
Compressing could save 1.8KiB (12% reduction).

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

Your page has 2 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.Optimize CSS Delivery of the following:,400,500,700

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:******ytics.js (2 hours)

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 <a href="" class="pill hollow video">▶ Check here</a> is close to 1 other tap targets .
The tap target <button class="pill hollow">Close</button> is close to 1 other tap targets .

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 525B (50% reduction).

Compressing could save 525B (50% reduction).

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 492B (47% reduction).

Minifying could save 492B (47% reduction) after compression.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? does not use compression.
Original size: 14.17 KB
Compressed size: n/a
File reduced by: n/a

+ 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: Let's Encrypt Authority X3
Valid from: Jun 5 17:03:09 2019 GMT
Valid until: Sep 3 17:03:09 2019 GMT

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 09 Jun 2019 09:39:26 GMT
Connection: close
Server: Netlify
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
Content-Length: 220

+ DNS Lookup

Currently Not Available

+ 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-06-09T06:39:57-03:00

owner-c: PABEL76
admin-c: ACABR18
tech-c: MUM7
billing-c: ACABR18
nsstat: 20190609 AA
nslastaa: 20190609
nsstat: 20190609 AA
nslastaa: 20190609
nsstat: 20190609 AA
nslastaa: 20190609
nserver: ns-7***
nsstat: 20190609 AA
nslastaa: 20190609
created: 20041108 #1876420
changed: 20181113
expires: 20201108
status: published

nic-hdl-br: PABEL76
person: Pablo Bello
created: 20180404
changed: 20190227

nic-hdl-br: ACABR18
created: 20180215
changed: 20180215

nic-hdl-br: MUM7
person: Murilo Mello
created: 20000303
changed: 20170714

% 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 305 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
6 secs
57 secs
1 min
1 min
2 mins
3 mins
3 mins
3 mins
4 mins
4 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

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