Fb.ru - SEO Checker - Website Review

Your Website Score is

Similar Ranking

UCLA

ucla.edu

СМОТРЕТЬ ФИЛЬМЫ ОНЛАЙН В ХОРОШЕМ КАЧЕСТВЕ, КИНО И ВИДЕО ФИЛЬМЫ МОЖНО СМОТРЕТЬ У НАС НА САЙТЕ. НЕ МОЖЕТЕ СКАЧАТЬ НОВИНКИ – СМОТРИТЕ ФИЛЬМЫ В ОНЛАЙН КИНОТЕАТРЕ IVI ПРЯМО СЕЙЧАС!

ivi.ru

ФЕДЕРАЛЬНОЕ АГЕНТСТВО НОВОСТЕЙ. НОВОСТИ СО ВСЕГО МИРА

riafan.ru

THE ADVERTISING PLATFORM FOR THE OPEN INTERNET | CRITEO

criteo.com

EL PAPA PIDE PERDÓN POR PERDER LA PACIENCIA CON UNA PEREGRINA EN EL VATICANO

aciprensa.com

SNAP--- - THE FASTEST WAY TO SHARE A MOMENT!

snap---.com

WE ARE WHAT WE DO | MEETUP

meetup.com

Latest Sites

THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ

noithatmanhhe.vn

SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP

nhacanhothongminh.com

CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM

crypto-mining.biz

99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING

999dice.com

RELANDICE BOT FOR 999DICE

relandice.com

❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !

baophong.vn

ONE MORE STEP

seeking.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

89 fb.ru Last Updated: 10 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 89%

Best Practices Desktop Score 85%

SEO Desktop Score 91%

Progressive Web App Desktop Score 27%

Performance Mobile Score 49%

Best Practices Mobile Score 85%

SEO Mobile Score 91%

Progressive Web App Mobile Score 30%

Page Authority Authority 56%

Domain Authority Domain Authority 91%

Moz Rank 5.6/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 5 Characters

FB.RU

Meta Description 0 Characters

NO DATA

Effective URL 13 Characters

https://fb.ru

Excerpt Page content

FB.ru Автомобили ...

Keywords Cloud Density

которые17 чтобы14 фото14 года13 новости11 ученые11 время11 люди10 автомобили9 когда9

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

Keyword	Freq	Title	Desc	Domain	H1	H2
которые	17
чтобы	14
фото	14
года	13
новости	11
ученые	11
время	11
люди	10
автомобили	9
когда	9

Google Preview Your look like this in google search result

FB.RU

https://fb.ru

FB.ru Автомобили ...

Robots.txt File Detected

http://fb.ru/robots.txt

Sitemap.xml File Detected

http://fb.ru/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: 1970-01-01 / 51 years

Create on: 1997-10-16 / 23 years

Expires on: 2019-10-31 / 10 months 27 days

RU-CENTER-RU ,

Nameservers

ns1.selectel.org.

ns2.selectel.org.

ns3.selectel.org.

ns4.selectel.org.

Page Size Code & Text Ratio

Document Size: ~160.42 KB

Code Size: ~58.64 KB

Text Size: ~101.78 KB Ratio: 63.45%

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

Minimizes main-thread work 1.0 s

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

First Contentful Paint 0.9 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 14 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

Avoid an excessive DOM size 973 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)

Minify JavaScript Potential savings of 3 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.9 s

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

Keep request counts low and transfer sizes small 82 requests • 3,789 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 65 resources found

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

Max Potential First Input Delay 70 ms

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

Time to Interactive 1.3 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.8 s

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

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

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

Reduce server response times (TTFB) Root document took 720 ms

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

Eliminate render-blocking resources Potential savings of 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 208 KB

Optimized images load faster and consume less cellular data

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

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

JavaScript execution time 0.3 s

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

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

Properly size images Potential savings of 2,893 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 1.9 s

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

First CPU Idle 1.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).

Avoid enormous network payloads Total size was 3,789 KB

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

Mobile

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

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

Eliminate render-blocking resources Potential savings of 840 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 208 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 860 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 810 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.9 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 3,275 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

Properly size images Potential savings of 692 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 4.9 s

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

First CPU Idle 5.1 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).

Avoid enormous network payloads Total size was 3,725 KB

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

Minimize main-thread work 4.8 s

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

First Contentful Paint 2.9 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 10 chains found

Avoid an excessive DOM size 973 elements

Minify JavaScript Potential savings of 3 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 3.1 s

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

Keep request counts low and transfer sizes small 78 requests • 3,725 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 65 resources found

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

Max Potential First Input Delay 320 ms

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

Time to Interactive 16.4 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 16.4 s

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

First Contentful Paint (3G) 6044.5 ms

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

Estimated Input Latency 120 ms

Tap targets are not sized appropriately 97% 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 100% 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 25 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 548 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

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
Server: nginx
Date: Wed, 27 Nov 2019 10:25:40 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Keep-Alive: timeout=70
Vary: Accept-Encoding
Set-Cookie: fbru=5c0ppctnfnpoe5g4782rsuod4stjpoea; expires=Fri, 27-Dec-2019 10:25:40 GMT; Max-Age=2592000; path=/; domain=.fb.ru; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Set-Cookie: a=me8YfBe2Q4wjBv075btdZ8O1oJCktyiQC9hpE1nuUC-CWVFdW5hLBPBS-eObJzc7jA0IkT-wLP8up2L3EBU; expires=Tue, 22-Nov-2039 10:25:40 GMT; Max-Age=630720000; path=/; domain=.fb.ru; HttpOnly
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	fb.ru	92.53.85.58	IN	6602
NS	fb.ru	ns3.selectel.org	IN	6662
NS	fb.ru	ns2.selectel.org	IN	6662
NS	fb.ru	ns1.selectel.org	IN	6662
NS	fb.ru	ns4.selectel.org	IN	6662
MX	fb.ru	aspmx.l.google.com	IN	6662
MX	fb.ru	aspmx2.googlemail.com	IN	6662
MX	fb.ru	alt1.aspmx.l.google.com	IN	6662
MX	fb.ru	aspmx3.googlemail.com	IN	6662
MX	fb.ru	alt2.aspmx.l.google.com	IN	6662
MX	fb.ru	aspmx4.googlemail.com	IN	6662
TXT	fb.ru	v=spf1 a mx ip4:31.131.253.16/29 ip4:92.53.85.56/29 ip4:95.213.188.72/29 include:_spf.google.com ?all	IN	6662

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

89 fb.ru Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Google Font API

Liveinternet

Nginx

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