Elbruto.Es - Info elbruto.es

elbruto.es receives about 1,866 unique visitors and 16,611 (8.90 per visitor) page views per day which should earn about $2.23/day from advertising revenue. Estimated site value is $1,308.99. According to Alexa Traffic Rank elbruto.es is ranked number 344,652 in the world and 0.00011% of global Internet users visit it. Site is hosted in France and links to network IP address 178.32.123.64. This server doesn't support HTTPS and doesn't support HTTP/2.

About - elbruto.es

El Bruto
Edit Site Info

Technologies used on Website

Currently Not Available

elbruto.es Profile

Title: El Bruto
Keywords: el,bruto
Last update was 249 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is elbruto.es?

1.9K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,866
Monthly Unique Visitors:
44,784
Pages per Visit:
8.90
Daily Pageviews:
16,611
Alexa Rank:
344,652 visit alexa
Alexa Reach:
0.00011%   (of global internet users)
Avg. visit duration:
02:46
Bounce rate:
23.24%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
42.36%
Referral:
1.71%
Search:
55.63%
Social:
0.30%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Bolivia 25.0%21.3%1241

Where do visitors go on this site?

Reach%Pageviews%PerUser
elbruto.es
56.01%9.05%2
fazvi123.elbruto.es
25.00%21.29%9
OTHER
0%69.66%0

Competitive Data

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

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is elbruto.es?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

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


Mobile summary

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

+ Abusive Experience Report

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

+ How much elbruto.es can earn?

Daily Revenue:
$2.23
Monthly Revenue:
$66.90
Yearly Revenue:
$813.95
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Bolivia 3,538$2.23

How much money do elbruto.es lose due to Adblock?

Daily Revenue Loss:
$0.09
Monthly Revenue Loss:
$2.67
Yearly Revenue Loss:
$32.54
Daily Pageviews Blocked:
142
Monthly Pageviews Blocked:
4,246
Yearly Pageviews Blocked:
51,657
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Bolivia 142$0.09

How much is elbruto.es worth?

Website Value:
$1,308.99

+ Where is elbruto.es hosted?

Server IP:
178.32.123.64
ASN:
AS16276 
ISP:
OVH SAS 
Server Location:

France, FR
 

Other sites hosted on 178.32.123.64

+ How fast does elbruto.es load?

Average Load Time:
(681 ms) 91 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

99
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)2.2s 67% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 67% 24% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 24% 8% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 8%
First Input Delay (FID)11ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 1% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

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)2.3s 65% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 65% 25% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 25% 8% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 8%
First Input Delay (FID)11ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 97% 1% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 1% 1% of loads for this page have a slow (>250ms) First Input Delay (FID) 1%

Lab Data

Max Potential First Input Delay 30 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 0.5 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.5 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 0.5 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 0.5 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.

Eliminate render-blocking resources - Potential savings of 40 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.

URL
SizePotential Savings
http://data.elbruto.es/css/style.css?v=20
6 KB190
http://data.elbruto.es/css/es.css?v=20
1 KB190
http://data.elbruto.es/js/app.js?v=18
21 KB270
http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700&subset=latin,cyrillic
1 KB190
Efficiently encode images - Potential savings of 5 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://data.elbruto.es/img//es/head.jpg
49 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://elbruto.es/
0 ms743 ms3 KB7 KB200text/htmlDocument
http://data.elbruto.es/css/style.css?v=20
757 ms1219 ms6 KB29 KB200text/cssStylesheet
http://data.elbruto.es/css/es.css?v=20
757 ms1295 ms1 KB1 KB200text/cssStylesheet
http://data.elbruto.es/js/app.js?v=18
758 ms1374 ms21 KB87 KB200application/javascriptScript
http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700&subset=latin,cyrillic
758 ms767 ms1 KB3 KB200text/cssStylesheet
http://data.braziball.com/img/logo_small.png
758 ms1032 ms0 KB0 KB404text/plainImage
http://data.braziball.com/img/player01.png
758 ms1221 ms0 KB0 KB404text/plainImage
http://data.braziball.com/img/puzzle_pub.png
1033 ms1189 ms0 KB0 KB404text/plainImage
http://data.braziball.com/img/player02.png
1190 ms1650 ms0 KB0 KB404text/plainImage
http://www.twinoid.com/img/lang/es/app_google.png
1222 ms1646 ms0 KB0 KB302text/html
http://www.twinoid.com/img/lang/es/appStore.png
1384 ms1811 ms0 KB0 KB302text/html
http://data.elbruto.es/img/es/etre_une_brute.gif
1384 ms1576 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/es/ou_pas.gif
1384 ms1767 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/sq/mush_es.gif
1384 ms1529 ms17 KB17 KB200image/gifImage
http://data.elbruto.es/img/sq/teacher_es1.gif
1384 ms1557 ms40 KB39 KB200image/gifImage
http://data.elbruto.es/img/motiontwin.gif
1384 ms1552 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/gradientBG.jpg
1389 ms1989 ms1 KB0 KB200image/jpegImage
http://data.elbruto.es/img//es/head.jpg
1389 ms1853 ms50 KB49 KB200image/jpegImage
http://data.braziball.com/img/news_bg.jpg
1389 ms1554 ms0 KB0 KB404text/plainImage
http://data.elbruto.es/img/home_bg.gif
1390 ms1649 ms26 KB26 KB200image/gifImage
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMRw.woff2
1393 ms1397 ms16 KB16 KB200font/woff2Font
http://www.google-analytics.com/analytics.js
1406 ms1413 ms18 KB43 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j79&a=1054714290&t=pageview&_s=1&dl=http%3A%2F%2Felbruto.es%2F&ul=en-us&de=UTF-8&dt=El%20Bruto&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAAB~&jid=1883255333&gjid=440972201&cid=998003169.1569858457&tid=UA-114594-29&_gid=1555993480.1569858457&_r=1&z=1475537165
1447 ms1453 ms0 KB0 KB200image/gifImage
http://twinoid.com/img/lang/es/app_google.png
1646 ms2099 ms5 KB5 KB200image/pngImage
http://twinoid.com/img/lang/es/appStore.png
1811 ms2162 ms8 KB8 KB200image/pngImage
Serve static assets with an efficient cache policy - 14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://twinoid.com/img/lang/es/appStore.png
0 ms8 KB
http://twinoid.com/img/lang/es/app_google.png
0 ms5 KB
http://data.elbruto.es/img//es/head.jpg
7200000 ms50 KB
http://data.elbruto.es/img/sq/teacher_es1.gif
7200000 ms40 KB
http://data.elbruto.es/img/home_bg.gif
7200000 ms26 KB
http://data.elbruto.es/js/app.js?v=18
7200000 ms21 KB
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://data.elbruto.es/img/sq/mush_es.gif
7200000 ms17 KB
http://data.elbruto.es/css/style.css?v=20
7200000 ms6 KB
http://data.elbruto.es/img/motiontwin.gif
7200000 ms1 KB
http://data.elbruto.es/img/es/etre_une_brute.gif
7200000 ms1 KB
http://data.elbruto.es/img/es/ou_pas.gif
7200000 ms1 KB
http://data.elbruto.es/img/gradientBG.jpg
7200000 ms1 KB
http://data.elbruto.es/css/es.css?v=20
7200000 ms1 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB25 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
767 ms
9 ms
778 ms
5 ms
1401 ms
8 ms
1409 ms
17 ms
1431 ms
8 ms
1443 ms
26 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.

URL
Potential Savings
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMRw.woff2
4 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
90 ms3 ms1 ms
Remove unused CSS - Potential savings of 6 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.

URL
SizePotential Savings
http://data.elbruto.es/css/style.css?v=20
6 KB6 KB
Avoids enormous network payloads - Total size was 218 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://data.elbruto.es/img//es/head.jpg
50 KB
http://data.elbruto.es/img/sq/teacher_es1.gif
40 KB
http://data.elbruto.es/img/home_bg.gif
26 KB
http://data.elbruto.es/js/app.js?v=18
21 KB
http://www.google-analytics.com/analytics.js
18 KB
http://data.elbruto.es/img/sq/mush_es.gif
17 KB
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMRw.woff2
16 KB
http://twinoid.com/img/lang/es/appStore.png
8 KB
http://data.elbruto.es/css/style.css?v=20
6 KB
http://twinoid.com/img/lang/es/app_google.png
5 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
43 ms
Script Evaluation
32 ms
Style & Layout
23 ms
Rendering
12 ms
Parse HTML & CSS
7 ms
Script Parsing & Compilation
5 ms
Garbage Collection
0 ms
Serve images in next-gen formats - Potential savings of 26 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.

URL
SizePotential Savings
http://data.elbruto.es/img//es/head.jpg
49 KB26 KB
Avoids an excessive DOM size - 57 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](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
57
Maximum DOM Depth
13
Maximum Child Elements
6
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://data.elbruto.es/js/app.js?v=18
21 KB3 KB
Keep request counts low and transfer sizes small - 25 requests • 218 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
25218 KB
Image
16152 KB
Script
238 KB
Font
116 KB
Stylesheet
38 KB
Document
13 KB
Other
21 KB
Media
00 KB
Third-party
1351 KB
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.

Reduce server response times (TTFB) - Root document took 740 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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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)2.8s 67% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 42% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 42% 14% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 14%
First Input Delay (FID)269ms 1% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 82% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 82% 15% of loads for this page have a slow (>250ms) First Input Delay (FID) 15%

Origin Data

All pages served from this origin have an SLOW 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)2.8s 43% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 43% 42% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 42% 14% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 14%
First Input Delay (FID)269ms 97% of loads for this page have a fast (<50ms) First Input Delay (FID) 1% 82% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 82% 15% of loads for this page have a slow (>250ms) First Input Delay (FID) 15%

Lab Data

First CPU Idle 1.8 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.8 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 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 60 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 1.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 3402 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.
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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

URL
Size
http://data.elbruto.es/img/sq/Capman.gif
107 KB
http://data.elbruto.es/img//es/head.jpg
50 KB
http://data.elbruto.es/img/home_bg.gif
26 KB
http://data.elbruto.es/js/app.js?v=18
21 KB
http://www.google-analytics.com/analytics.js
18 KB
http://data.elbruto.es/img/sq/mush_es.gif
17 KB
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
10 KB
http://twinoid.com/img/lang/es/appStore.png
8 KB
http://data.elbruto.es/css/style.css?v=20
6 KB
http://twinoid.com/img/lang/es/app_google.png
5 KB
Minimizes main-thread work - 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
162 ms
Script Evaluation
143 ms
Style & Layout
88 ms
Parse HTML & CSS
32 ms
Rendering
32 ms
Script Parsing & Compilation
21 ms
Serve images in next-gen formats - Potential savings of 26 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.

URL
SizePotential Savings
http://data.elbruto.es/img//es/head.jpg
49 KB26 KB
Avoids an excessive DOM size - 57 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](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
57
Maximum DOM Depth
13
Maximum Child Elements
6
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://data.elbruto.es/js/app.js?v=18
21 KB3 KB
Keep request counts low and transfer sizes small - 25 requests • 280 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
25280 KB
Image
16219 KB
Script
238 KB
Font
110 KB
Stylesheet
38 KB
Document
13 KB
Other
21 KB
Media
00 KB
Third-party
1345 KB
Use video formats for animated content - Potential savings of 49 KB
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.

URL
SizePotential Savings
http://data.elbruto.es/img/sq/Capman.gif
107 KB49 KB
Eliminate render-blocking resources - Potential savings of 490 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.

URL
SizePotential Savings
http://data.elbruto.es/css/style.css?v=20
6 KB780
http://data.elbruto.es/css/es.css?v=20
1 KB630
http://data.elbruto.es/js/app.js?v=18
21 KB1080
http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700&subset=latin,cyrillic
1 KB630
Efficiently encode images - Potential savings of 5 KB
Optimized images load faster and consume less cellular data. Learn more.

URL
SizePotential Savings
http://data.elbruto.es/img//es/head.jpg
49 KB5 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://elbruto.es/
0 ms507 ms3 KB7 KB200text/htmlDocument
http://data.elbruto.es/css/style.css?v=20
520 ms579 ms6 KB29 KB200text/cssStylesheet
http://data.elbruto.es/css/es.css?v=20
520 ms557 ms1 KB1 KB200text/cssStylesheet
http://data.elbruto.es/js/app.js?v=18
521 ms716 ms21 KB87 KB200application/javascriptScript
http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700&subset=latin,cyrillic
521 ms549 ms1 KB3 KB200text/cssStylesheet
http://data.braziball.com/img/logo_small.png
521 ms561 ms0 KB0 KB429text/plainImage
http://data.braziball.com/img/player01.png
521 ms561 ms0 KB0 KB429text/plainImage
http://data.braziball.com/img/puzzle_pub.png
561 ms597 ms0 KB0 KB429text/plainImage
http://data.braziball.com/img/player02.png
562 ms622 ms0 KB0 KB404text/plainImage
http://www.twinoid.com/img/lang/es/app_google.png
597 ms813 ms0 KB0 KB302text/html
http://www.twinoid.com/img/lang/es/appStore.png
624 ms921 ms0 KB0 KB302text/html
http://data.elbruto.es/img/es/etre_une_brute.gif
728 ms759 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/es/ou_pas.gif
728 ms760 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/sq/Capman.gif
728 ms795 ms107 KB107 KB200image/gifImage
http://data.elbruto.es/img/sq/mush_es.gif
728 ms759 ms17 KB17 KB200image/gifImage
http://data.elbruto.es/img/motiontwin.gif
728 ms768 ms1 KB1 KB200image/gifImage
http://data.elbruto.es/img/gradientBG.jpg
735 ms768 ms1 KB0 KB200image/jpegImage
http://data.elbruto.es/img//es/head.jpg
736 ms819 ms50 KB49 KB200image/jpegImage
http://data.braziball.com/img/news_bg.jpg
736 ms948 ms0 KB0 KB404text/plainImage
http://data.elbruto.es/img/home_bg.gif
737 ms788 ms26 KB26 KB200image/gifImage
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
740 ms744 ms10 KB10 KB200font/woff2Font
http://www.google-analytics.com/analytics.js
754 ms759 ms18 KB43 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j79&a=1012241012&t=pageview&_s=1&dl=http%3A%2F%2Felbruto.es%2F&ul=en-us&de=UTF-8&dt=El%20Bruto&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAAAB~&jid=1439870147&gjid=8972242&cid=79315971.1569858450&tid=UA-114594-29&_gid=50077271.1569858450&_r=1&z=1120854026
801 ms805 ms0 KB0 KB200image/gifImage
http://twinoid.com/img/lang/es/app_google.png
813 ms1108 ms5 KB5 KB200image/pngImage
http://twinoid.com/img/lang/es/appStore.png
921 ms1141 ms8 KB8 KB200image/pngImage
Serve static assets with an efficient cache policy - 14 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://twinoid.com/img/lang/es/appStore.png
0 ms8 KB
http://twinoid.com/img/lang/es/app_google.png
0 ms5 KB
http://data.elbruto.es/img/sq/Capman.gif
7200000 ms107 KB
http://data.elbruto.es/img//es/head.jpg
7200000 ms50 KB
http://data.elbruto.es/img/home_bg.gif
7200000 ms26 KB
http://data.elbruto.es/js/app.js?v=18
7200000 ms21 KB
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
http://data.elbruto.es/img/sq/mush_es.gif
7200000 ms17 KB
http://data.elbruto.es/css/style.css?v=20
7200000 ms6 KB
http://data.elbruto.es/img/motiontwin.gif
7200000 ms1 KB
http://data.elbruto.es/img/es/etre_une_brute.gif
7200000 ms1 KB
http://data.elbruto.es/img/es/ou_pas.gif
7200000 ms1 KB
http://data.elbruto.es/img/gradientBG.jpg
7200000 ms1 KB
http://data.elbruto.es/css/es.css?v=20
7200000 ms1 KB
Third-Party Usage - 1 Third-Party Found
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.

Third-Party
SizeMain Thread Time
18 KB118 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
531 ms
8 ms
743 ms
11 ms
754 ms
19 ms
777 ms
5 ms
792 ms
30 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.

URL
Potential Savings
http://fonts.gstatic.com/s/opensanscondensed/v14/z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuXMR7eS2Ao.woff2
4 ms
JavaScript execution time - 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
331 ms14 ms4 ms
http://www.google-analytics.com/analytics.js
118 ms111 ms6 ms
Remove unused CSS - Potential savings of 6 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.

URL
SizePotential Savings
http://data.elbruto.es/css/style.css?v=20
6 KB6 KB
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.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. 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.

Server response times are low (TTFB) - Root document took 510 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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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

Your page has 1 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:

http://data.elbruto.es/js/app.js?v=18
Optimize CSS Delivery of the following:

http://data.elbruto.es/css/style.css?v=20
http://data.elbruto.es/css/es.css?v=20
http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700&subset=latin,cyrillic

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Tu lector Flas…á actualizado. and 1 others render only 5 pixels tall (13 CSS pixels) .
Haz clic aquí…a actualizarlo renders only 5 pixels tall (13 CSS pixels) .
Pon un nombre…n... EL BRUTO. and 1 others render only 5 pixels tall (13 CSS pixels) .
¿Ya estás inscrito? renders only 6 pixels tall (15 CSS pixels) .
Más juegos: and 6 others render only 5 pixels tall (13 CSS pixels) .
© 2009 renders only 5 pixels tall (13 CSS pixels) .

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="http://www.bra…nternal_launch"></a> is close to 1 other tap targets .
The tap target <a href="https://play.g…nternal_launch"></a> and 1 others are close to other tap targets .
The tap target <input type="text" name="name"> is close to 3 other tap targets .
The tap target <input type="submit"> is close to 2 other tap targets .
The tap target <a href="http://trax.mo…o_link/arka_es">Arkadeo</a> and 6 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:

http://twinoid.com/img/lang/es/appStore.png (expiration not specified)
http://twinoid.com/img/lang/es/app_google.png (expiration not specified)
http://data.elbruto.es/css/es.css?v=20 (2 hours)
http://data.elbruto.es/css/style.css?v=20 (2 hours)
http://data.elbruto.es/img//es/head.jpg (2 hours)
http://data.elbruto.es/img/es/etre_une_brute.gif (2 hours)
http://data.elbruto.es/img/es/ou_pas.gif (2 hours)
http://data.elbruto.es/img/gradientBG.jpg (2 hours)
http://data.elbruto.es/img/home_bg.gif (2 hours)
http://data.elbruto.es/img/motiontwin.gif (2 hours)
http://data.elbruto.es/img/sq/mush_es.gif (2 hours)
http://data.elbruto.es/img/sq/teacher_es1.gif (2 hours)
http://data.elbruto.es/js/app.js?v=18 (2 hours)
http://www.google-***ytics.com/***ytics.js (2 hours)

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Optimize images

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

Optimize the following images to reduce their size by 20.3KiB (33% reduction).

Compressing http://data.elbruto.es/img//es/head.jpg could save 14.9KiB (31% reduction).
Compressing http://twinoid.com/img/lang/es/appStore.png could save 3.8KiB (50% reduction).
Compressing http://twinoid.com/img/lang/es/app_google.png could save 1.4KiB (29% reduction).
Compressing http://data.elbruto.es/img/motiontwin.gif could save 148B (13% 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.
Enable compression
You have compression enabled. Learn more about enabling compression.
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 HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does elbruto.es use compression?

elbruto.es use gzip compression.
Original size: 6.78 KB
Compressed size: 2.68 KB
File reduced by: 4.1 KB (60%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  90
Vendor reliability:
  90
Privacy:
  90
Child safety:
  89

+ SSL Checker - SSL Certificate Verify

elbruto.es does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

elbruto.es does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Mon, 30 Sep 2019 15:47:19 GMT
Server: Apache
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Expires: Mon, 26 Jul 1997 05:00:00 GMT
P3P: CP="ALL DSP COR NID CURa OUR STP PUR"
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 2740
Content-Type: text/html; Charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
SOA 300
Mname ns0.motion-twin.com
Rname hostmaster.elbruto.es
Serial Number 17030300
Refresh 3600
Retry 900
Expire 604800
Minimum TTL 0
MX spool.mail.gandi.net 300
MX fb.mail.gandi.net 300
A 178.32.123.64 277
NS ns1.motion-twin.com 300
NS ns2.motion-twin.com 300
NS ns0.motion-twin.com 300

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.nic.es...
Conditions of use for the whois service via port 43 for .es domains

Access will only be enabled for IP addresses authorised by Red.es. A maximum of one IP address per
user/organisation is permitted.

Red.es accepts no responsibility whatsoever for the availability of access to WHOIS, which may be
suspended at any time and without prior warning at the discretion of the public entity.

The service will be limited to the data established by Red.es.

The user promises to make use of the service and to carry out any action derived from the aforesaid
use in accordance with current applicable regulations, in particular with legislation on “.es” domain
names and personal data protection.

In particular, the user undertakes not to use the service to carry out abusive or speculative domain
name registrations, pursuant to section 5 of the Sixth Additional Provision of Law 34/2002, of 11 July,
on Services of the Information Society and Electronic Commerce. Likewise, the User undertakes not to
use the service to obtain data, the possession of which may contravene the provisions of Organic Law
15/1999, of 13 December, on Personal Data Protection, and its Regulations, or in Law 34/2002, of 11
July, on Services of the Information Society and Electronic Commerce.

Failure to comply with these conditions will result in the immediate withdrawal of the service and any
registered domain name which breaches said conditions may be officially cancelled by Red.es.
-------------------------------------------------------------------------------------------------------


The IP address used to perform the query is not authorised or has exceeded the established limit for
queries.To request access to the service,complete the form located at https://sede.red.gob.es/sede/whois,
where you may also consult the service conditions.

-------------------------------------------------------------------------------------------------------
More information on each domain may be consulted at www.dominios.es.
Last update was 249 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

baza-gai.com.ua
47 secs
skypaybd.com
1 min
autobooking.com
1 min
lobstertaxi.com
1 min
arenalviv.com.ua
2 mins
alfagro.com.ua
3 mins
anex-tour.com.ua
4 mins
free4mobile24.com
5 mins
munaexpress.net
5 mins
mangakik.com
6 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

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) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
elbruto.es widget