Subtitulos.Guru - Info subtitulos.guru

subtitulos.guru receives about 9,526 unique visitors and 16,194 (1.70 per visitor) page views per day which should earn about $5.73/day from advertising revenue. Estimated site value is $4,184.84. According to Alexa Traffic Rank subtitulos.guru is ranked number 305,556 in the world and 0.00021% of global Internet users visit it. Site is hosted in United States and links to network IP address 104.18.39.191. This server supports HTTPS and HTTP/2.

About - subtitulos.guru


Technologies used on Website

CDN
CloudFlare
Programming Languages
PHP

subtitulos.guru Profile

Title: Subtítulos en español
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is subtitulos.guru?

9.5K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
9,526
Monthly Unique Visitors:
228,624
Pages per Visit:
1.70
Daily Pageviews:
16,194
Alexa Rank:
305,556 visit alexa
Alexa Reach:
0.00021%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
Mexico 19.1%20.3%11289
Argentina 12.2%13.2%9540

Where do visitors go on this site?

Reach%Pageviews%PerUser
subtitulos.guru
100.00%100.00%1.7

Competitive Data

SEMrush
Domain:
  subtitulos.guru
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 subtitulos.guru?

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:
subtitulos.guru
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:
subtitulos.guru
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 subtitulos.guru can earn?

Daily Revenue:
$5.73
Monthly Revenue:
$171.90
Yearly Revenue:
$2,091.45
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
Mexico 3,287$3.19
Argentina 2,138$2.54

How much money do subtitulos.guru lose due to Adblock?

Daily Revenue Loss:
$0.64
Monthly Revenue Loss:
$19.29
Yearly Revenue Loss:
$234.74
Daily Pageviews Blocked:
595
Monthly Pageviews Blocked:
17,854
Yearly Pageviews Blocked:
217,222
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Argentina 299$0.36
Mexico 296$0.29

How much is subtitulos.guru worth?

Website Value:
$4,184.84

+ Where is subtitulos.guru hosted?

Server IP:
104.18.39.191
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.18.39.191

+ How fast does subtitulos.guru load?

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

Page Speed (Google PageSpeed Insights) - Desktop

100
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.1s 66% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 66% 29% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 29% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)10ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.2s 61% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 61% 34% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 34% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)12ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.3 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.3 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.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
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.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

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
56 ms3 ms1 ms
Avoids enormous network payloads - Total size was 51 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.googletagmanager.com/gtag/js?id=UA-5559254-89
28 KB
https://www.google-analytics.com/analytics.js
18 KB
https://subtitulos.guru/
4 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1523078807&t=pageview&_s=1&dl=https%3A%2F%2Fsubtitulos.guru%2F&ul=en-us&de=windows-1252&dt=Subt%C3%ADtulos%20en%20espa%C3%B1ol&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=2022878267&gjid=1143874508&cid=771020038.1575330558&tid=UA-5559254-89&_gid=1021597012.1575330558&_r=1>m=2ouav9&z=1353510326
1 KB
http://subtitulos.guru/
0 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. Learn more.

Category
Time Spent
Script Evaluation
44 ms
Style & Layout
28 ms
Other
16 ms
Script Parsing & Compilation
5 ms
Rendering
5 ms
Parse HTML & CSS
3 ms
Garbage Collection
1 ms
Avoids an excessive DOM size - 216 elements
A large DOM will 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
216
Maximum DOM Depth
6
Maximum Child Elements
205
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://subtitulos.guru/)
0
https://subtitulos.guru/
190
Keep request counts low and transfer sizes small - 5 requests • 51 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
551 KB
Script
246 KB
Document
14 KB
Image
11 KB
Other
10 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
346 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://subtitulos.guru/
0 ms190 ms0 KB0 KB301text/html
https://subtitulos.guru/
190 ms497 ms4 KB24 KB200text/htmlDocument
https://www.googletagmanager.com/gtag/js?id=UA-5559254-89
510 ms529 ms28 KB73 KB200application/javascriptScript
https://www.google-analytics.com/analytics.js
567 ms573 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1523078807&t=pageview&_s=1&dl=https%3A%2F%2Fsubtitulos.guru%2F&ul=en-us&de=windows-1252&dt=Subt%C3%ADtulos%20en%20espa%C3%B1ol&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=2022878267&gjid=1143874508&cid=771020038.1575330558&tid=UA-5559254-89&_gid=1021597012.1575330558&_r=1>m=2ouav9&z=1353510326
605 ms610 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.

URL
Cache TTLSize
https://www.google-analytics.com/analytics.js
7200000 ms18 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.

Third-Party
SizeMain-Thread Blocking Time
28 KB0 ms
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
525 ms
8 ms
538 ms
33 ms
577 ms
6 ms
584 ms
9 ms
602 ms
29 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

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.

Serve images in next-gen formats
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.

Avoid chaining critical requests - 1 chain 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 310 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.


Page Speed (Google PageSpeed Insights) - Mobile

98
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.3s 66% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 60% 35% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 35% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)42ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.1s 69% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 69% 27% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 27% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)30ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 2% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

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.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 100 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 3.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 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2160 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.1 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.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 216 elements
A large DOM will 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
216
Maximum DOM Depth
6
Maximum Child Elements
205
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://subtitulos.guru/)
0
https://subtitulos.guru/
630
Keep request counts low and transfer sizes small - 5 requests • 51 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
551 KB
Script
246 KB
Document
14 KB
Image
11 KB
Other
11 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Third-party
346 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://subtitulos.guru/
0 ms224 ms1 KB0 KB301text/html
https://subtitulos.guru/
224 ms527 ms4 KB24 KB200text/htmlDocument
https://www.googletagmanager.com/gtag/js?id=UA-5559254-89
543 ms565 ms28 KB73 KB200application/javascriptScript
https://www.google-analytics.com/analytics.js
614 ms624 ms18 KB43 KB200text/javascriptScript
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1932319445&t=pageview&_s=1&dl=https%3A%2F%2Fsubtitulos.guru%2F&ul=en-us&de=windows-1252&dt=Subt%C3%ADtulos%20en%20espa%C3%B1ol&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=1338660457&gjid=1701841586&cid=447296277.1575330553&tid=UA-5559254-89&_gid=43208231.1575330553&_r=1>m=2ouav9&z=1070458589
651 ms656 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.

URL
Cache TTLSize
https://www.google-analytics.com/analytics.js
7200000 ms18 KB
Minimize third-party usage - Third-party code blocked the main thread for 30 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.

Third-Party
SizeMain-Thread Blocking Time
19 KB34 ms
28 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
558 ms
9 ms
573 ms
8 ms
582 ms
35 ms
624 ms
7 ms
632 ms
11 ms
655 ms
25 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.

URL
Total CPU TimeScript EvaluationScript Parse
Other
278 ms15 ms5 ms
https://www.google-analytics.com/analytics.js
96 ms91 ms6 ms
https://www.googletagmanager.com/gtag/js?id=UA-5559254-89
73 ms62 ms11 ms
Avoids enormous network payloads - Total size was 51 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
https://www.googletagmanager.com/gtag/js?id=UA-5559254-89
28 KB
https://www.google-analytics.com/analytics.js
18 KB
https://subtitulos.guru/
4 KB
https://www.google-analytics.com/r/collect?v=1&_v=j79&a=1932319445&t=pageview&_s=1&dl=https%3A%2F%2Fsubtitulos.guru%2F&ul=en-us&de=windows-1252&dt=Subt%C3%ADtulos%20en%20espa%C3%B1ol&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=1338660457&gjid=1701841586&cid=447296277.1575330553&tid=UA-5559254-89&_gid=43208231.1575330553&_r=1>m=2ouav9&z=1070458589
1 KB
http://subtitulos.guru/
1 KB
Minimizes main-thread work - 0.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
169 ms
Style & Layout
139 ms
Other
77 ms
Rendering
26 ms
Script Parsing & Compilation
23 ms
Parse HTML & CSS
17 ms
Serve images in next-gen formats
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.

Avoid chaining critical requests - 1 chain 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 300 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.

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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

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="X2***911-s01e03.html" class="tags_font">911 s01e03</a> and 49 others are close to other tap targets .
The tap target <a href="X2***abominable-2019.html" class="tags_font">abominable 2019</a> and 3 others are close to other tap targets .
The tap target <a href="X2***angel-has-fallen-2019.html" class="tags_font">angel has fallen 2019</a> and 2 others are close to other tap targets .
The tap target <a href="X2***freaks-2018.html" class="tags_font">freaks 2018</a> and 4 others are close to other tap targets .
The tap target <a href="X2***his-dark-materials.html" class="tags_font">his dark materials</a> and 4 others are close to other tap targets .
The tap target <a href="X2***his-dark-m…ls-s01e05.html" class="tags_font">his dark materials s01e05</a> and 6 others are close to other tap targets .
The tap target <a href="X2***interstellar-2014.html" class="tags_font">interstellar 2014</a> and 8 others are close to other tap targets .
The tap target <a href="X2***mandalorian.html" class="tags_font">mandalorian</a> and 1 others are close to other tap targets .
The tap target <a href="X2***rambo:-las…lood-2019.html" class="tags_font">rambo: last blood 2019</a> and 1 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:

https://www.googletagmanager.com/gtag/js?id=UA-5559254-89 (15 minutes)
https://www.google-***ytics.com/***ytics.js (2 hours)

Reduce server response time

In our test, your server responded in 0.27 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
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.
Enable compression
You have compression enabled. Learn more about enabling compression.
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.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
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.
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 subtitulos.guru use compression?

subtitulos.guru use br compression.
Original size: 23.84 KB
Compressed size: 4.02 KB
File reduced by: 19.82 KB (83%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

subtitulos.guru supports HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

subtitulos.guru supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Mon, 02 Dec 2019 23:49:03 GMT
Content-Type: text/html; charset=ISO-8859-1
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=da3312bac9b28919ac8fc7350e440858b1575330543; expires=Wed, 01-Jan-20 23:49:03 GMT; path=/; domain=.subtitulos.guru; HttpOnly
X-Powered-By: PHP/5.3.3
Location: https://subtitulos.guru/
X-Cache: HIT from Backend
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 53f131f8095ac647-MSP

HTTP/2 200 
date: Mon, 02 Dec 2019 23:49:03 GMT
content-type: text/html; charset=ISO-8859-1
set-cookie: __cfduid=d42c7889cae2dc7330a62cc319930e8721575330543; expires=Wed, 01-Jan-20 23:49:03 GMT; path=/; domain=.subtitulos.guru; HttpOnly
x-powered-by: PHP/5.3.3
vary: Accept-Encoding
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 53f131f99e3fc637-MSP
content-encoding: br

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 104.18.39.191 282
A 104.18.38.191 282
NS kate.ns.cloudflare.com 3582
NS paul.ns.cloudflare.com 3582

+ Whois Lookup

Domain Created:
2019-09-23
Domain Age:
2 months 9 days  
WhoIs:
 

whois lookup at whois.donuts.co...
Domain Name: subtitulos.guru
Registry Domain ID: 5404a524aeee46c18b6ffd8688868b00-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: https://www.namecheap.com/
Updated Date: 2019-09-28T14:34:57Z
Creation Date: 2019-09-23T14:34:11Z
Registry Expiry Date: 2020-09-23T14:34:11Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: WhoisGuard, Inc.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Panama
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: PA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: kate.ns.cloudflare.com
Name Server: paul.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-12-02T23:49:21Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Donuts Inc. provides this Whois service for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Donuts does not guarantee its accuracy. Users accessing the Donuts Whois service agree to use the data only for lawful purposes, and under no cir***stances may this data be used to: a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the registrar’s own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Donuts or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Donuts Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data can be requested by submitting a request via the form found at https://donuts.domains/about/policies/whois-layered-access/ Donuts Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Last update was 3 days ago
loader
This can take up to 60 seconds. Please wait...

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

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!
subtitulos.guru widget