Your Website Score is

Similar Ranking

14
SHABAKIEH CO.
shabakieh.com
14
موتور جستجوی قطره
ghatreh.com
14
گاما | نمونه سوال امتحانی | آزمون آنلاین | پاورپوینت | کلاس آنلاین | درسنامه آموزشی | مدرسه یاب | معلم خصوصی
gama.ir
14
آرمان هلث - فروش مستقیم محصولات پزشکی
arman-health.ir
14
صنایع روشنایی حسام صنعت شرق
hesamsanat.com
14
مرجع تخصصی محصولات اینترنتی – وی آی پی پک – بزرگترین و مورد اعتمادترین مرجع محصولات اینترنتی
vip-pack.com
14
سامانه الکترونیکی کار و اقامت
atba.ir

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

14 adacostore.ir Last Updated: 1 month

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

Desktop

Mobile

Performance Desktop Score 43%
Best Practices Desktop Score 87%
SEO Desktop Score 75%
Progressive Web App Desktop Score 27%
Performance Mobile Score 21%
Best Practices Mobile Score 80%
SEO Mobile Score 77%
Progressive Web App Mobile Score 33%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 23 Characters
صفحه اصلی - آداکو استور
Meta Description 0 Characters
NO DATA
Effective URL 20 Characters
http://adacostore.ir
Excerpt Page content
صفحه اصلی - آداکو استور ...
Keywords Cloud Density
خرید38 font33 افزودن30 unit30 فروشگاهی27 size26 پرینتر25 title23 ریال19 true16
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
خرید 38
font 33
افزودن 30
unit 30
فروشگاهی 27
size 26
پرینتر 25
title 23
ریال 19
true 16
Google Preview Your look like this in google search result
صفحه اصلی - آداکو استور
http://adacostore.ir
صفحه اصلی - آداکو استور ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~243.44 KB
Code Size: ~190.08 KB
Text Size: ~53.36 KB Ratio: 21.92%

Desktop

Desktop Screenshot
JavaScript execution time 0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS Potential savings of 86 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
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Minimize main-thread work 2.2 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.255
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify JavaScript Potential savings of 7 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoids enormous network payloads Total size was 2,034 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats Potential savings of 761 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
Reduce initial server response time Root document took 1,710 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid an excessive DOM size 1,251 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 chaining critical requests 47 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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Largest Contentful Paint 4.5 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
Time to Interactive 4.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 86 resources found
A long cache lifetime can speed up repeat visits to your page
First CPU Idle 2.2 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/).
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
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Defer offscreen images Potential savings of 86 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Eliminate render-blocking resources Potential savings of 2,530 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid non-composited animations 15 animated elements found
Animations which are not composited can be janky and increase CLS
Does not use HTTPS 89 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
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
Efficiently encode images Potential savings of 252 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 2.1 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Keep request counts low and transfer sizes small 90 requests • 2,034 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Properly size images Potential savings of 534 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

Mobile

Mobile Screenshot
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
Estimated Input Latency 60 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 13.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Eliminate render-blocking resources Potential savings of 6,430 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 7.0 s
First Contentful Paint marks the time at which the first text or image is painted
Document uses legible font sizes 95.06% 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 1,920 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 8.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Avoid chaining critical requests 47 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
Max Potential First Input Delay 440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Properly size images Potential savings of 187 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Serve images in next-gen formats Potential savings of 532 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
Total Blocking Time 610 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 11.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Does not use HTTPS 79 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 13.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Cumulative Layout Shift 0.094
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images Potential savings of 292 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Serve static assets with an efficient cache policy 76 resources found
A long cache lifetime can speed up repeat visits to your page
Efficiently encode images Potential savings of 87 KiB
Optimized images load faster and consume less cellular data
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small 80 requests • 1,663 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads Total size was 1,663 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid an excessive DOM size 1,251 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 CPU Idle 7.1 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/).
Remove unused CSS Potential savings of 87 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
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Reduce JavaScript execution time 2.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minify CSS Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint (3G) 13904 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Tap targets are not sized appropriately 83% 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
First Meaningful Paint 7.1 s
First Meaningful Paint measures when the primary content of a page is visible
Minify JavaScript Potential savings of 7 KiB
Minifying JavaScript files can reduce payload sizes and script parse time

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
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
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
adacostore.co Available Buy Now!
adacostore.us Available Buy Now!
adacostore.com Available Buy Now!
adacostore.org Available Buy Now!
adacostore.net Available Buy Now!
aacostore.ir Available Buy Now!
qdacostore.ir Available Buy Now!
zdacostore.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
Content-Type: text/html; charset=UTF-8
Link: ; rel="https://api.w.org/"
Link: ; rel="alternate"; type="application/json"
Link: ; rel=shortlink
Cache-Control: public, max-age=0
Expires: Sun, 16 May 2021 12:26:58 GMT
Date: Sun, 16 May 2021 12:26:58 GMT
DNS Records DNS Resource Records associated with a hostname
View DNS Records