Your Website Score is

Similar Ranking

19
ورزش سه‌ :: صفحه اصلی
varzesh3.com
19
نمونه سوالات پیام نور، نهایی، کنکور و نمونه سوال‌های استخدامی | بانک سوال
soal-bank.ir
19
ایران صدا .::. دانلود آهنگ جدید
ir-seda.com
19
آژانس مسافرتی فارا گشت کوروش کبیر (مجری اصلی تورهای مسافرتی)
faragasht.com
19
تحصیل در روسیه | پذیرش 100% تضمینی از دانشگاه های مورد تایید - روس دانش
rusdanesh.com
19
کلینیک خانه سفید - کلینیک خانه سفید
whcl.ir
19
تماشای آنلاین فیلم و سریال
filimo.com

Latest Sites

31
خرید و فروش کتاب های دست دوم | درسی | دانشگاهی | رمان - پیک کاغذی
peykekaghazi.com
29
باما، میان‌بر به بازار خودرو | BAMA
bama.ir
31
خرید و فروش ملک - املاکا
amlakaa.com
31
خرید و فروش ملک - املاکا
amlakaa.ir
19
سپید مووی | دانلود رایگان فیلم و سریال با لینک مستقیم
sepidmovie.xyz
2
ترمووود | ترمو وود | ترموود | چوب ترمووود | نمای ترمووود | پارس وود
parswoodco.com

Top Technologies

WordPress
CMS
Google Font API
Font Scripts
Yoast SEO
SEO
LiteSpeed
Web Servers
Font Awesome
Font Scripts
WooCommerce
Ecommerce
Apache
Web Servers
CloudFlare
CDN

19 subf2m.ir Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 94%
Best Practices Desktop Score 86%
SEO Desktop Score 83%
Progressive Web App Desktop Score 52%
Performance Mobile Score 69%
Best Practices Mobile Score 79%
SEO Mobile Score 81%
Progressive Web App Mobile Score 54%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 39 Characters
دانلود زیرنویس فارسی و انگلیسی | SUBF2M
Meta Description 99 Characters
دانلود زیرنویس فارسی با انواع تنظیمات و استایل ,زیرنویس فیلم , زیرنویس سریال و انواع موزیک ویدئو ها
Effective URL 17 Characters
https://subf2m.ir
Excerpt Page content
دانلود زیرنویس فارسی و انگلیسی | subf2m subf2m 3.0 جستجوی زیرنویس جستجوی زیرنویس ...
Keywords Cloud Density
زیرنویس19 arabic13 subtitle11 spider8 wafed798 english7 subf2m6 subtitles6 فارسی6 فیلم6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
زیرنویس 19
arabic 13
subtitle 11
spider 8
wafed79 8
english 7
subf2m 6
subtitles 6
فارسی 6
فیلم 6
Google Preview Your look like this in google search result
دانلود زیرنویس فارسی و انگلیسی | SUBF2M
https://subf2m.ir
دانلود زیرنویس فارسی با انواع تنظیمات و استایل ,زیرنویس فیلم , زیرنویس سریال و انواع موزیک ویدئو ها
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~23.47 KB
Code Size: ~11.42 KB
Text Size: ~12.06 KB Ratio: 51.36%

Social Data

Delicious Total: 0
Facebook Total: 0
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

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

Technologies

PWA - Manifest



The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param gcm_sender_id
103953800507
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest

Desktop

Desktop Screenshot
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Keep request counts low and transfer sizes small 38 requests • 444 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size 341 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)
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images Potential savings of 4 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Remove unused CSS Potential savings of 14 KiB
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 79 KiB
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
Avoids enormous network payloads Total size was 444 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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
Reduce initial server response time Root document took 910 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.228
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page
First CPU Idle 0.7 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/).
Time to Interactive 0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible
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
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
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
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

Mobile

Mobile Screenshot
Largest Contentful Paint 6.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Keep request counts low and transfer sizes small 36 requests • 664 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 240 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Includes front-end JavaScript libraries with known security vulnerabilities 9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
First Contentful Paint (3G) 3990 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 12 KiB
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
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 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
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
Avoid long main-thread tasks 5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Eliminate render-blocking resources Potential savings of 1,120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint 2.0 s
First Meaningful Paint measures when the primary content of a page is visible
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
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
Time to Interactive 4.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 341 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)
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Minimizes main-thread work 1.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.394
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are not sized appropriately 35% 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
Remove unused CSS Potential savings of 14 KiB
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
Defer offscreen images Potential savings of 27 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to 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
Use video formats for animated content Potential savings of 132 KiB
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
First CPU Idle 3.8 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 664 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript Potential savings of 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Document uses legible font sizes 99.89% 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
Reduce initial server response time Root document took 670 ms
Keep the server response time for the main document short because all other requests depend on it
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes

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
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is 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
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
subf2m.co Already Registered
subf2m.us Available Buy Now!
subf2m.com Already Registered
subf2m.org Available Buy Now!
subf2m.net Already Registered
sbf2m.ir Available Buy Now!
wubf2m.ir Available Buy Now!
xubf2m.ir Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Connection: Keep-Alive
X-Powered-By: PHP/5.6.40
Content-Type: text/html; charset=utf-8
cache-control: private
cf-cache-status: DYNAMIC
cf-request-id: 05d5901bfb00000b88702fb000000001
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report?lkg-colo=20&lkg-time=1602894628"}],"group":"cf-nel","max_age":604800}
nel: {"report_to":"cf-nel","max_age":604800}
cf-ray: 5e35e93ffbb90b88-AMS
Date: Sat, 17 Oct 2020 04:08:14 GMT
Server: LiteSpeed
Alt-Svc: quic=":443"; ma=2592000; v="43,46", h3-Q043=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-25=":443"; ma=2592000, h3-27=":443"; ma=2592000
DNS Records DNS Resource Records associated with a hostname
View DNS Records