Your Website Score is

Similar Ranking

12
ЗАПЧАСТИ JOHNSTON,BUCHER,EPOKE,МВП,МВПК,ЭД,МКДУ, ДИСКИ ЩЕТОЧНЫЕ - ГЛАВНАЯ СТРАНИЦА
speccomzap.ru
12
فانی فان
fanefan.ir
12
LOVE MARRIAGE PROBLEM SOLUTION AND HUSBAND WIFE RELATIONSHIP ASTROLOGY
ptgopalshastri.com
12
HOUSE & OFFICE SHIFTING SERVICE IN DHAKA - ROYAL MOVERS BD.
royal-movers.com
12
SISTEMAS CONTRA INCENDIOS QUITO ECUADOR - REDES HIDRICAS QUITO ECUADOR - RECARGA EXTINTORES QUITO ECUADOR - GABINETES CONTRA INCENDIOS QUITO ECUADOR - TUBERIAS DE ALIMENTACION DE SISTEMAS CONTRA INCEN
systececuador.com
12
ДАЙВИНГ НА КИПРЕ - РУССКИЙ ДАЙВЦЕНТР В ЛАРНАКЕ!
rustydivers.com
12
PERSONAL & COMPANY PROFILE PLATFORM | BOOKMARKING & BLOG POST
iwebpoint.com

Latest Sites

1
-
copiadoraboavista.com.br
1
-
cironaparaiba.com.br
34
60 SECONDS BOOT RANK TURBO ONLINE WEBSITE REVIEWER
turbo-reviewer.60-s.de
1
-
audit.freesmartseo.com
1
-
csswoke.ga
29
VISIT OUR OFFICIAL SITE
xeroneit.co
47
DIGITAL SIGNATURE | SIGNATURE CERTIFICATE ONLINE SERVICE (DSC) IN INDIA – RADIUM SIGN
buydigitalsignature.com

Top Technologies

PHP
Programming Languages
Google Font API
Font Scripts
WordPress
CMS
jQuery
JavaScript Frameworks
Font Awesome
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Apache
Web Servers
Twitter Bootstrap
Web Frameworks
Yoast SEO
SEO

12 fanefan.ir Last Updated: 7 months

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

Desktop

Mobile

Performance Desktop Score 84%
Best Practices Desktop Score 67%
SEO Desktop Score 73%
Progressive Web App Desktop Score 0%
Performance Mobile Score 46%
Best Practices Mobile Score 60%
SEO Mobile Score 62%
Progressive Web App Mobile Score 0%
Page Authority Authority 28%
Domain Authority Domain Authority 7%
Moz Rank 2.8/10
Bounce Rate Rate 0%
Title Tag 9 Characters
فانی فان
Meta Description 28 Characters
فانی فان,فانی فان , فانی فان
Effective URL 21 Characters
http://www.fanefan.ir
Excerpt Page content
فانی فان فانی فان خانه انجمن پروفایل ثبت نام تبلیغات سایت تفریحی ف...
Meta Keywords 3 Detected
فانی فان فانی فان فانی فان
Keywords Cloud Density
دانلود50 بازی36 خنده36 غمگین35 عاشقانه34 جدید31 برای26 انیمیشن25 کوتاه18 سایت16
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
دانلود 50
بازی 36
خنده 36
غمگین 35
عاشقانه 34
جدید 31
برای 26
انیمیشن 25
کوتاه 18
سایت 16
Google Preview Your look like this in google search result
فانی فان
http://www.fanefan.ir
فانی فان,فانی فان , فانی فان
Robots.txt File Detected
http://fanefan.ir/robots.txt
Sitemap.xml File Detected
http://fanefan.ir/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~134.42 KB
Code Size: ~133.86 KB
Text Size: ~568 B Ratio: 0.41%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Properly size images Potential savings of 101 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Enable text compression Potential savings of 6 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid chaining critical requests 8 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
Defer offscreen images Potential savings of 58 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Does not use HTTPS 49 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Time to Interactive 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Reduce initial server response time Root document took 1,320 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 883 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images Potential savings of 29 KiB
Optimized images load faster and consume less cellular data
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 55 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid serving legacy JavaScript to modern browsers Potential savings of 24 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 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 130 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
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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Keep request counts low and transfer sizes small 67 requests • 883 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid an excessive DOM size 1,090 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)
Cumulative Layout Shift 0.029
Cumulative Layout Shift measures the movement of visible elements within the viewport
Use video formats for animated content Potential savings of 75 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
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Mobile

Mobile Screenshot
Cumulative Layout Shift 0.025
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Reduce the impact of third-party code Third-party code blocked the main thread for 1,750 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
Reduce unused JavaScript Potential savings of 55 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Does not use HTTPS 49 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Reduce initial server response time Root document took 1,180 ms
Keep the server response time for the main document short because all other requests depend on it
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
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Keep request counts low and transfer sizes small 67 requests • 881 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Total Blocking Time 1,820 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 24 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
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid an excessive DOM size 1,090 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)
Serve images in next-gen formats Potential savings of 130 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
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
Serve static assets with an efficient cache policy 38 resources found
A long cache lifetime can speed up repeat visits to your page
Use video formats for animated content Potential savings of 75 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
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 6.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid long main-thread tasks 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Max Potential First Input Delay 770 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads Total size was 881 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 8 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
Efficiently encode images Potential savings of 29 KiB
Optimized images load faster and consume less cellular data
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive 6.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint (3G) 2934 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Reduce JavaScript execution time 1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
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
Warning! Your website is not SSL secured (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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links
First 20 Links Relationship HTTP Status
Homepage Internal Link 200
Forum Internal Link 200
Profile Internal Link 200
Register Internal Link 200
ads Internal Link 301
Rss Internal Link 200
تبلیغات Internal Link 301
مطالب Internal Link 200
دانلود Internal Link 302
پیامک Internal Link 302
طنز Internal Link 302
گالری تصاویر Internal Link 302
اخبار Internal Link 302
داستان Internal Link 302
خالکوپی Internal Link 200
زناشویی Internal Link 200
آپدیت آنتی ویروس Internal Link 302
جديد ترين قيمت هادر ايران Internal Link 302
کدآهنگ پيشواز Internal Link 302
قالب وبلاگ Internal Link 302

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

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
Keep-Alive: timeout=5, max=100
set-cookie: PHPSESSID=1370a62e5a4dfdedc520e4dc7319b2fe; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
content-language: fa
content-type: text/html; charset=utf-8
date: Fri, 25 Jun 2021 11:31:59 GMT
server: LiteSpeed
strict-transport-security: max-age=0;
vary: User-Agent
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A fanefan.ir 79.127.127.68 IN 14051
NS fanefan.ir ns2.rozblog.com IN 86400
NS fanefan.ir ns1.rozblog.com IN 86400
MX fanefan.ir fanefan.ir IN 14400

About Us

Contact Info

Follow Us

Copyright - ProRank.co | All Right Reserved
Languages | English
Add extension to Chrome