Your Website Score is

Similar Ranking

2
CANVA
canva.com
2
h.k.p.com
2
MSN
msn.com
2
320ytmp3.com.
2
---HUBER.CO - THIS WEBSITE IS FOR SALE! - ---HUBER RESOURCES AND INFORMATION.
beegcom.club
2
JUST A MOMENT...
kinks.ca
2
mauropozzer.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
14
-
coloressence.com

Top Technologies

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

2 persianfood.us Last Updated: 5 months

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 75%
SEO Desktop Score 91%
Performance Mobile Score 81%
Best Practices Mobile Score 76%
SEO Mobile Score 91%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 21 Characters
http://persianfood.us
Google Preview Your look like this in google search result
persianfood.us
http://persianfood.us
Robots.txt File Detected
http://persianfood.us/robots.txt
Sitemap.xml File Detected
http://persianfood.us/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN
Text Size: ~1 B Ratio: 100.00%

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
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
Does not use HTTPS 46 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 1.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Avoids enormous network payloads Total size was 1,460 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused CSS Est savings of 95 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid serving legacy JavaScript to modern browsers Est savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Improve image delivery Est savings of 710 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Properly size images Est savings of 293 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Avoid chaining critical requests 28 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
Minify CSS Est savings of 14 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.1 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Initial server response time was short Root document took 200 ms
Keep the server response time for the main document short because all other requests depend on it
Minify JavaScript Est savings of 17 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoids an excessive DOM size 276 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)
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
Eliminate render-blocking resources Est savings of 390 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve images in next-gen formats Est savings of 610 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused JavaScript Est savings of 48 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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
Largest Contentful Paint element 1,470 ms
This is the largest contentful element painted within the viewport
Serve static assets with an efficient cache policy 45 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Use efficient cache lifetimes Est savings of 2,184 KiB
A long cache lifetime can speed up repeat visits to your page
Efficiently encode images Est savings of 416 KiB
Optimized images load faster and consume less cellular data

Mobile

Mobile Screenshot
Time to Interactive 3.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify CSS Est savings of 14 KiB
Minifying CSS files can reduce network payload sizes
Serve static assets with an efficient cache policy 44 resources found
A long cache lifetime can speed up repeat visits to your page
Minify JavaScript Est savings of 17 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoids an excessive DOM size 277 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.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Use efficient cache lifetimes Est savings of 2,179 KiB
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Est savings of 1,660 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Est savings of 654 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Cumulative Layout Shift 0.155
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 28 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 large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Improve image delivery Est savings of 797 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP
Avoids enormous network payloads Total size was 1,455 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Efficiently encode images Est savings of 416 KiB
Optimized images load faster and consume less cellular data
Largest Contentful Paint element 3,400 ms
This is the largest contentful element painted 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
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
Initial server response time was short Root document took 230 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid serving legacy JavaScript to modern browsers Est savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/baseline) features, unless you know you must support legacy browsers
Reduce unused CSS Est savings of 94 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Serve images in next-gen formats Est savings of 610 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 45 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
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
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 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce unused JavaScript Est savings of 48 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity

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
Warning! Your website is not SSL secured (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
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 0 Links Relationship HTTP Status

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
persianfood.co Available
persianfood.us Available
persianfood.com Already Registered
persianfood.org Already Registered
persianfood.net Already Registered
prsianfood.us Available
lersianfood.us Available

Information Server

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


						

					

						


						
									


			
			
			
		
		

		
	





    
     

  

    

            
About Us


      We provide SEO metrics for your website.
There are many who have trusted on us and improved their position thanks to our recommendations
      
    


    

            
Contact Info

                         
 RYIN

             
                        
 10407 Feeney Trafficway Apt. 577

             
                        
 Maryland Line

                                    
 1-760-992-3170

                                                 
 [email protected]

                


   
    

            
Follow Us

            
                        
 Facebook

             
            
                                         


 
    

    

      
© Copyright 2023

    



       

         Languages | 

                        
                                                     English