Your Website Score is

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

1 emway.ir Last Updated: 2 weeks

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

Desktop

Mobile

Performance Desktop Score 66%
Best Practices Desktop Score 64%
SEO Desktop Score 82%
Progressive Web App Desktop Score 44%
Performance Mobile Score 47%
Best Practices Mobile Score 62%
SEO Mobile Score 85%
Progressive Web App Mobile Score 46%
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 15 Characters
http://emway.ir
Google Preview Your look like this in google search result
emway.ir
http://emway.ir
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~1 B
Code Size: ~NAN B
Text Size: ~1 B Ratio: 100.00%

Social Data

Delicious Total: 0
Facebook Total: 3
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

Desktop

Desktop Screenshot
Time to Interactive 2.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Efficiently encode images Potential savings of 295 KiB
Optimized images load faster and consume less cellular data
Serve images in next-gen formats Potential savings of 1,124 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
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
Does not use HTTPS 1 insecure request 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 servedover 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
Avoid enormous network payloads Total size was 3,075 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.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 1,410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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 Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images Potential savings of 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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 element 1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift 0.132
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
Keep request counts low and transfer sizes small 85 requests • 3,075 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Avoids an excessive DOM size 523 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 Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 73 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 48 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
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
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 2.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid multiple page redirects Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded
First CPU Idle 1.5 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 30 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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Properly size images Potential savings of 1,615 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce initial server response time Root document took 1,080 ms
Keep the server response time for the main document short because all other requests depend on it

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
Avoid enormous network payloads Total size was 3,086 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 7.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First CPU Idle 5.0 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/).
Efficiently encode images Potential savings of 295 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 4.3 s
First Contentful Paint marks the time at which the first text or image is painted
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
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
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 9.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 4.8 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 3.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 3,830 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused CSS Potential savings of 30 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 12 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify JavaScript Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Contentful Paint (3G) 8273.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Time to Interactive 8.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests 51 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
Total Blocking Time 140 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 1,274 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Initial server response time was short Root document took 160 ms
Keep the server response time for the main document short because all other requests depend on it
Document uses legible font sizes 98.85% 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
Serve images in next-gen formats Potential savings of 1,122 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
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
Serve static assets with an efficient cache policy 71 resources found
A long cache lifetime can speed up repeat visits to your page
Does not use HTTPS 1 insecure request 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 servedover 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
Avoid multiple page redirects Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded
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
Keep request counts low and transfer sizes small 84 requests • 3,086 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size 514 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)
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
Max Potential First Input Delay 110 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay

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

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
emway.co Available Buy Now!
emway.us Available Buy Now!
emway.com Already Registered
emway.org Already Registered
emway.net Already Registered
eway.ir Available Buy Now!
xmway.ir Available Buy Now!
dmway.ir Already Registered

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 307 Temporary Redirect
Server: ArvanCloud
Date: Thu, 15 Oct 2020 14:34:29 GMT
Content-Type: text/html
Content-Length: 0
Location: http://emway.ir/
Connection: keep-alive
Set-Cookie: __arcsco=6594740f6619da9210f4435616359de9; Path=/; HttpOnly; Max-Age=10000; Domain=emway.ir
AR-PoweredBy: Arvan Cloud (arvancloud.com)
AR-ATIME: 0.001
AR-Request-ID: dbdc635799183a53d929f0a86f9def17
AR-SID: 6101
DNS Records DNS Resource Records associated with a hostname
View DNS Records