Your Website Score is

Similar Ranking

46
بخور زار | بخور زار
par3bezanim.ir
46
همفکر ساری، گفتگوی سازنده!
hamfekrsari.ir
46
کادوپینو IS COMING SOON
kadopino.com
46
موتور جست و جو ایرانی | VITM | فناوری اطلاعات و رسانه ولیعصر
vitm.ir
46
БОЛЬШОЕ ТАКСИ ИЗ АЭРОПОРТА ТОЛМАЧЕВО В ДРУГОЙ ГОРОД | СКИДКИ
taxi-iz-tolmachevo.ru
46
ورق کامپوزیت - طلوع باند
toloobond.com
46
سایت ساز اینتر | سایت ساز اینتر
sitesazinter.net

Latest Sites

14
MAINHOME » مدیران
m88.ir
1

Top Technologies

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

46 mhadimirdamadi.ir Last Updated: 3 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 89%
Best Practices Desktop Score 87%
SEO Desktop Score 83%
Progressive Web App Desktop Score 45%
Performance Mobile Score 88%
Best Practices Mobile Score 87%
SEO Mobile Score 86%
Progressive Web App Mobile Score 50%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 45 Characters
MOHAMMAD HADI MIRDAMADI | محمد هادی میردامادی
Meta Description 162 Characters
Mohammad Hadi Mirdamadi - Translator, Designer, Full Stack Web Programmer and Developer | محمد هادی میردامادی - مترجم، طراح، توسعه دهنده و برنامه نویس فول استک وب
Effective URL 25 Characters
https://mhadimirdamadi.ir
Excerpt Page content
Mohammad Hadi Mirdamadi | محمد هادی میردامادی ...
Keywords Cloud Density
design10 visit9 translation8 وبسایت7 site5 programming5 english4 language4 more3 ۱۳۹۹3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
design 10
visit 9
translation 8
وبسایت 7
site 5
programming 5
english 4
language 4
more 3
۱۳۹۹ 3
Google Preview Your look like this in google search result
MOHAMMAD HADI MIRDAMADI | محمد هادی میردامادی
https://mhadimirdamadi.ir
Mohammad Hadi Mirdamadi - Translator, Designer, Full Stack Web Programmer and Developer | محمد هادی میردامادی - مترجم، طراح، توسعه دهنده و برنامه نویس
Robots.txt File Detected
Sitemap.xml File No Found
Page Size Code & Text Ratio
Document Size: ~42.35 KB
Code Size: ~26.03 KB
Text Size: ~16.32 KB Ratio: 38.54%

Desktop

Desktop Screenshot
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle 0.6 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/).
Minimizes main-thread work 0.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 1,361 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Initial server response time was short Root document took 580 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Remove unused CSS Potential savings of 33 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
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 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 16 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 enormous network payloads Total size was 3,139 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
robots.txt is not valid 10 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
Cumulative Layout Shift 0.009
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible
Efficiently encode images Potential savings of 249 KiB
Optimized images load faster and consume less cellular data
Serve static assets with an efficient cache policy 48 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small 49 requests • 3,139 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
Eliminate render-blocking resources Potential savings of 70 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 372 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)
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
Serve images in next-gen formats Potential savings of 947 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
Avoid non-composited animations 15 animated elements found
Animations which are not composited can be janky and increase CLS
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

Mobile

Mobile Screenshot
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
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint (3G) 2430 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid enormous network payloads Total size was 3,139 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 430 ms
Keep the server response time for the main document short because all other requests depend on it
First CPU Idle 2.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/).
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
Keep request counts low and transfer sizes small 49 requests • 3,139 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve images in next-gen formats Potential savings of 1,079 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
Largest Contentful Paint 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 2.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift 0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport
Serve static assets with an efficient cache policy 48 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 50 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Efficiently encode images Potential savings of 249 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 2.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid non-composited animations 15 animated elements found
Animations which are not composited can be janky and increase CLS
Properly size images Potential savings of 651 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids an excessive DOM size 372 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)
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 16 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
Remove unused CSS Potential savings of 33 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
Eliminate render-blocking resources Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
robots.txt is not valid 10 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
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
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

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
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Warning! Not 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
Congratulations! Your site not 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

Domain Available

Domain (TDL) and Typo Status
mhadimirdamadi.co Available Buy Now!
mhadimirdamadi.us Available Buy Now!
mhadimirdamadi.com Available Buy Now!
mhadimirdamadi.org Available Buy Now!
mhadimirdamadi.net Available Buy Now!
madimirdamadi.ir Available Buy Now!
jhadimirdamadi.ir Available Buy Now!
ihadimirdamadi.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
Set-Cookie: PHPSESSID=c7aa1qrlcbn0s71akjm3qkac70; path=/; secure
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Content-Type: text/html; charset=UTF-8
Date: Tue, 23 Mar 2021 11:08:33 GMT
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