Your Website Score is

Similar Ranking

94
FACEBOOK - LOG IN OR SIGN UP
facebook.com
94
AMAZON.COM: ONLINE SHOPPING FOR ELECTRONICS, APPAREL, COMPUTERS, BOOKS, DVDS & MORE
amazon.com
94
FACEBOOK – LOG IN OR SIGN UP
l.facebook.com
94
FACEBOOK - INICIA SESIÓN O REGÍSTRATE
es-la.facebook.com
94
VIMEO INTERACTIVE VIDEO EXPERIENCE PLATFORM
vimeo.com
94
VK | WELCOME!
vk.com

Latest Sites

19
SENILE TEAM DEV LOG
senileteam.com
14
BOXHERO.IN
boxhero.in
21
HUYCHESS
huychess.sbs
96
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
19
YUPPOW - FREE HD MOVIES AND TV SHOWS STREAMING ONLINE
yuppow.org

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
WordPress
CMS

94 m.facebook.com Last Updated: 8 months

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 96%
Best Practices Desktop Score 78%
SEO Desktop Score 100%
Performance Mobile Score 94%
Best Practices Mobile Score 92%
SEO Mobile Score 75%
PWA Mobile Score 60%
Page Authority Authority 93%
Domain Authority Domain Authority 96%
Moz Rank 9.3/10
Bounce Rate Rate 0%
Title Tag 5 Characters
ERROR
Meta Description 0 Characters
NO DATA
Effective URL 92 Characters
https://m.facebook.com/login.php?next=https%3A%2F%2Fm.facebook.com%2F&refsrc=deprecated&_rdr
Excerpt Page content
ErrorFacebookFacebook is not available on this browserTo continue using Facebook, get one of the browsers below.Learn moreEnglish (UK) + Meta © 2025
Keywords Cloud Density
facebook3 learn1 more1 english1 meta1 below1 browsers1 available1 browser1 continue1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
facebook 3
learn 1
more 1
english 1
meta 1
below 1
browsers 1
available 1
browser 1
continue 1
Google Preview Your look like this in google search result
ERROR
https://m.facebook.com/login.php?next=https%3A%2F%2Fm.facebook.com%2F&refsrc=deprecated&_rdr
ErrorFacebookFacebook is not available on this browserTo continue using Facebook, get one of the browsers below.Learn moreEnglish (UK) + Meta © 2025
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~6.61 KB
Code Size: ~6.46 KB
Text Size: ~155 B Ratio: 2.29%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Avoid serving legacy JavaScript to modern browsers Potential savings of 7 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources Potential savings of 410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid multiple page redirects Potential savings of 230 ms
Redirects introduce additional delays before the page can be loaded
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
Reduce unused JavaScript Potential savings of 64 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Network Round Trip Times 40 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
Largest Contentful Paint element 920 ms
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 570 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 351 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids an excessive DOM size 175 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)
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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
User Timing marks and measures 14 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Time to Interactive 1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests 4 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
Largest Contentful Paint 0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
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
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

Mobile

Mobile Screenshot
Keep request counts low and transfer sizes small 16 requests • 252 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Avoid chaining critical requests 4 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid serving legacy JavaScript to modern browsers Potential savings of 14 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
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
First Contentful Paint 2.2 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 1,230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint (3G) 4560 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint 2.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible
Tap targets are sized appropriately 100% 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
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
Reduce unused JavaScript Potential savings of 79 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoids an excessive DOM size 77 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)
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
robots.txt is not valid 13 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Avoids enormous network payloads Total size was 252 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Congratulations! Your site not have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Warning! You have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
m.facebook.co Already Registered
m.facebook.us Already Registered
m.facebook.com Already Registered
m.facebook.org Already Registered
m.facebook.net Already Registered
mfacebook.com Already Registered
j.facebook.com Already Registered
i.facebook.com Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Encoding: gzip
Set-Cookie: datr=GHSZZ0VGYubGsl9StX8WrGIV; expires=Thu, 05-Mar-2026 00:19:36 GMT; Max-Age=34560000; path=/; domain=.facebook.com; secure; httponly
Pragma: no-cache
Cache-Control: private, no-cache, no-store, must-revalidate
Expires: Sat, 01 Jan 2000 00:00:00 GMT
content-security-policy: default-src data: blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net;script-src *.facebook.com *.fbcdn.net *.facebook.net 127.0.0.1:* 'nonce-OzKgVMnt' blob: data: 'self' connect.facebook.net 'unsafe-eval' https://*.google-analytics.com *.google.com;style-src *.fbcdn.net data: *.facebook.com 'unsafe-inline' https://fonts.googleapis.com;connect-src *.facebook.com facebook.com *.fbcdn.net *.facebook.net wss://*.facebook.com:* wss://*.whatsapp.com:* wss://*.fbcdn.net attachment.fbsbx.com ws://localhost:* blob: *.cdninstagram.com 'self' http://localhost:3103 wss://gateway.facebook.com wss://edge-chat.facebook.com wss://snaptu-d.facebook.com wss://kaios-d.facebook.com/ v.whatsapp.net *.fbsbx.com *.fb.com https://*.google-analytics.com;font-src data: *.facebook.com *.fbcdn.net *.fbsbx.com https://fonts.gstatic.com;img-src *.fbcdn.net *.facebook.com data: https://*.fbsbx.com facebook.com *.cdninstagram.com fbsbx.com fbcdn.net connect.facebook.net *.carriersignal.info blob: android-webview-video-poster: *.whatsapp.net *.fb.com *.oculuscdn.com *.tenor.co *.tenor.com *.giphy.com https://paywithmybank.com/ https://*.paywithmybank.com/ https://www.googleadservices.com https://googleads.g.doubleclick.net https://*.google-analytics.com;media-src *.cdninstagram.com blob: *.fbcdn.net *.fbsbx.com www.facebook.com *.facebook.com data: *.tenor.co *.tenor.com https://*.giphy.com;frame-src *.facebook.com *.fbsbx.com fbsbx.com data: www.instagram.com *.fbcdn.net https://paywithmybank.com/ https://*.paywithmybank.com/ https://www.googleadservices.com https://googleads.g.doubleclick.net https://www.google.com https://td.doubleclick.net *.google.com *.doubleclick.net;worker-src blob: *.facebook.com data:;
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
error-mid: a54c0e145fa37b8c995a93956d45ceec
reporting-endpoints: coop_report="https://www.facebook.com/browser_reporting/coop/?minimize=0", default="https://m.facebook.com/ajax/mtouch_error_reports/?device_level=unknown&brsid=7465125504983481707"
report-to: {"max_age":2592000,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/coop\/?minimize=0"}],"group":"coop_report","include_subdomains":true}, {"max_age":259200,"endpoints":[{"url":"https:\/\/m.facebook.com\/ajax\/mtouch_error_reports\/?device_level=unknown&brsid=7465125504983481707"}]}
cross-origin-opener-policy: same-origin-allow-popups;report-to="coop_report"
origin-agent-cluster: ?1
accept-ch-lifetime: 4838400
accept-ch: viewport-width,dpr,Sec-CH-Prefers-Color-Scheme,Sec-CH-UA-Full-Version-List,Sec-CH-UA-Platform-Version,Sec-CH-UA-Model
Content-Type: text/html; charset=utf-8
Strict-Transport-Security: max-age=15552000; preload; includeSubDomains
X-FB-Debug: HlSQj3XDadNj/ZGq46IZvrMmJrv6jqZSd/b25WGCLvON1IMRMmoaUfO4MrkhvUKvIW+9qPkgOYyjW5Cu/OItDg==
Date: Wed, 29 Jan 2025 00:19:36 GMT
X-FB-Connection-Quality: EXCELLENT; q=0.9, rtt=7, rtx=0, c=10, mss=1380, tbw=141, tp=-1, tpl=-1, uplat=86, ullat=0
Alt-Svc: h3=":443"; ma=86400
Connection: keep-alive
DNS Records DNS Resource Records associated with a hostname
View DNS Records