Horriblesubs.info - SEO Checker

Your Website Score is

Similar Ranking

REZULTATI: NOGOMET, 1. HNL, PREMIER LEAGUE, SPORTSKI REZULTATI UŽIVO, LIVESCORE

rezultati.com

BERANDA | PORTAL RESMI PEMERINTAH PROVINSI DKI JAKARTA

jakarta.go.id

ДНЕВНИК.РУ

dnevnik.ru

慕课网-程序员的梦工厂

imooc.com

有声小说,听小说,有声书,在线听书电台-喜马拉雅FM

ximalaya.com

VITUX - LINUX COMPENDIUM

vitux.com

СПОРТ.UA ⇔ СВЕЖИЕ НОВОСТИ СПОРТА ОНЛАЙН ⋆ ВСЕ ПРО СПОРТ УКРАИНЫ И МИРА НА СЕГОДНЯ

sport.ua

Latest Sites

sha-256.io

JUST A MOMENT...

molla-tech.com

WELCOME TO BITHILS

bithils.com

GAMEAS

gameas.org

publishinglif.com

RICHSTORE

richstore.store

SPECIAL PRICE OFFER

newtaipeiqueen.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

29 horriblesubs.info Last Updated: 1 year

Success 55% of passed verification steps

Warning 15% of total warning

Errors 30% of total errors, require fast action

Mobile

Performance Desktop Score 71%

Best Practices Desktop Score 62%

SEO Desktop Score 82%

Progressive Web App Desktop Score 27%

Performance Mobile Score 30%

Best Practices Mobile Score 69%

SEO Mobile Score 80%

Progressive Web App Mobile Score 30%

Page Authority Authority 50%

Domain Authority Domain Authority 46%

Moz Rank 5.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 33 Characters

HORRIBLESUBS – SO BAD YET SO GOOD

Meta Description 0 Characters

NO DATA

Effective URL 25 Characters

https://horriblesubs.info

Excerpt Page content

HorribleSubs – So bad yet so good Skip to main content Toggle navigation HorribleSubs Shows Current Season Schedule IRC Guide IRC Channel Packlist FAQ Follow Us ...

Keywords Cloud Density

schedule3 horriblesubs2 giveaway2 current2 more2 neue1 full1 heroes1 past1 belated1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
schedule	3
horriblesubs	2
giveaway	2
current	2
more	2
neue	1
full	1
heroes	1
past	1
belated	1

Google Preview Your look like this in google search result

HORRIBLESUBS – SO BAD YET SO GOOD

https://horriblesubs.info

HorribleSubs – So bad yet so good Skip to main content Toggle navigation HorribleSubs Shows Current Season Schedule IRC Guide IRC Channel Packlist FAQ Follow Us ...

Robots.txt File Detected

http://horriblesubs.info/robots.txt

Sitemap.xml File No Found

http://horriblesubs.info/sitemap.xml

Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system

Updated: 2019-09-16 / 2 years

Create on: 2011-12-19 / 9 years

Expires on: 2020-12-19 / 4 months 1 days

easyDNS Technologies Inc. ,CA

Registrar Whois Server: whois.easydns.com

Registrar URL: http://www.easydns.com

Nameservers

DARA.NS.CLOUDFLARE.COM

BART.NS.CLOUDFLARE.COM

Page Size Code & Text Ratio

Document Size: ~21.02 KB

Code Size: ~14.59 KB

Text Size: ~6.43 KB Ratio: 30.58%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Manifest is not valid

Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Defer offscreen images Potential savings of 759 KB

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

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

Speed Index 1.9 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 3.4 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,997 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.7 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.0 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 25 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

Avoids an excessive DOM size 270 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)

First Meaningful Paint 1.1 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 82 requests • 2,022 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 29 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 150 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 4.0 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 16.3 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 30 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

Minify CSS Potential savings of 3 KB

Minifying CSS files can reduce network payload sizes

Remove unused CSS Potential savings of 62 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

Serve images in next-gen formats Potential savings of 935 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

Server response times are low (TTFB) Root document took 250 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 740 ms

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

Efficiently encode images Potential savings of 10 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 240 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

Total Blocking Time 230 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 1.6 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Estimated Input Latency 110 ms

First Contentful Paint (3G) 7654 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Minify CSS Potential savings of 3 KB

Minifying CSS files can reduce network payload sizes

Tap targets are not sized appropriately 61% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 90.38% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 63 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

Serve images in next-gen formats Potential savings of 840 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

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

Eliminate render-blocking resources Potential savings of 2,250 ms

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

Efficiently encode images Potential savings of 10 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 1,230 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

Total Blocking Time 710 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 3.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 47 KB

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

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

Speed Index 7.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 10.3 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 1,848 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.9 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 3.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 2 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 26 chains found

Avoids an excessive DOM size 227 elements

First Meaningful Paint 3.7 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 77 requests • 1,872 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 28 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 510 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 12.6 s

Time to interactive is the amount of time it takes for the page to become fully interactive

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

Page load is not fast enough on mobile networks Interactive at 12.6 s

A fast page load over a cellular network ensures a good mobile user experience

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Date: Thu, 28 Nov 2019 11:56:29 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=d0a8880c8211955debd24b1b2b64952061574942189; expires=Sat, 28-Dec-19 11:56:29 GMT; path=/; domain=.horriblesubs.info; HttpOnly
Vary: Accept-Encoding, Cookie
Cache-Control: max-age=3, must-revalidate
Strict-Transport-Security: max-age=0; includeSubdomains
X-Content-Type-Options: nosniff
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: 53cc28aa3949c514-ORD
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	horriblesubs.info	104.24.109.17	IN	265
A	horriblesubs.info	104.24.108.17	IN	265
NS	horriblesubs.info	bart.ns.cloudflare.com	IN	21599
NS	horriblesubs.info	dara.ns.cloudflare.com	IN	21599
MX	horriblesubs.info	aspmx.l.google.com	IN	299
MX	horriblesubs.info	alt1.aspmx.l.google.com	IN	299
MX	horriblesubs.info	alt2.aspmx.l.google.com	IN	299
MX	horriblesubs.info	alt3.aspmx.l.google.com	IN	299
MX	horriblesubs.info	alt4.aspmx.l.google.com	IN	299
AAAA	horriblesubs.info	2606:4700:30::6818:6d11	IN	265
AAAA	horriblesubs.info	2606:4700:30::6818:6c11	IN	265

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

29 horriblesubs.info Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

CloudFlare

Disqus

Google Font API

PHP

WordPress

WordPress Super Cache

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments