Tools & Wizards About Us
eways.ir screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

eways.ir

ایویز | فروش عمده لوازم جانبی موبایل و کامپیوتر

Page Load Speed

13.9 sec in total

First Response

2.3 sec

Resources Loaded

10.6 sec

Page Rendered

958 ms

eways.ir screenshot

About Website

Click here to check amazing Eways content for Iran. Otherwise, check out these important facts you probably never knew about eways.ir

دسترسی آسان به بازار لوازم جانبی موبایل و کامپیوتر و قیمت‌های رقابتی با ارسال به سراسر ایران

Visit eways.ir

Key Findings

We analyzed Eways.ir page load time and found that the first response time was 2.3 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

eways.ir performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value11.6 s

5/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

www.eways.ir

2323 ms

style.min.css

702 ms

theme.min.css

483 ms

header-footer.min.css

502 ms

custom-frontend-lite-rtl.min.css

675 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 97% of them (63 requests) were addressed to the original Eways.ir, 2% (1 request) were made to Google.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Eways.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.8 kB (21%)

Content Size

554.5 kB

After Optimization

440.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eways.ir main page is 554.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 196.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 112.0 kB

  • Original 142.1 kB
  • After minification 137.8 kB
  • After compression 30.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 112.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 196.0 kB
  • After minification 196.0 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Eways images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 298 B

  • Original 144.0 kB
  • After minification 144.0 kB
  • After compression 143.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.6 kB

  • Original 72.4 kB
  • After minification 72.4 kB
  • After compression 70.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Eways.ir has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (80%)

Requests Now

50

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eways. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.eways.ir

www.eways.ir

2323 ms

style.min.css

style.min.css

702 ms

theme.min.css

theme.min.css

483 ms

header-footer.min.css

header-footer.min.css

502 ms

custom-frontend-lite-rtl.min.css

custom-frontend-lite-rtl.min.css

675 ms

post-6.css

post-6.css

510 ms

feedzy-rss-feeds.css

feedzy-rss-feeds.css

527 ms

front-rtl.css

front-rtl.css

984 ms

style.css

style.css

1000 ms

swiper.min.css

swiper.min.css

1040 ms

custom-pro-frontend-lite-rtl.min.css

custom-pro-frontend-lite-rtl.min.css

1031 ms

font.css

font.css

1172 ms

all.min.css

all.min.css

1240 ms

v4-shims.min.css

v4-shims.min.css

1490 ms

global.css

global.css

1504 ms

post-1568.css

post-1568.css

1522 ms

jquery.min.js

jquery.min.js

1706 ms

jquery-migrate.min.js

jquery-migrate.min.js

1701 ms

flatpickr.min.js

flatpickr.min.js

1776 ms

flatpickr-mobile.js

flatpickr-mobile.js

2022 ms

v4-shims.min.js

v4-shims.min.js

2051 ms

custom-pro-widget-mega-menu-rtl.min.css

custom-pro-widget-mega-menu-rtl.min.css

2256 ms

custom-widget-icon-list-rtl.min.css

custom-widget-icon-list-rtl.min.css

2084 ms

custom-widget-icon-box-rtl.min.css

custom-widget-icon-box-rtl.min.css

2107 ms

widget-loop-builder-rtl.min.css

widget-loop-builder-rtl.min.css

2384 ms

animations.min.css

animations.min.css

2464 ms

hello-frontend.min.js

hello-frontend.min.js

2641 ms

imagesloaded.min.js

imagesloaded.min.js

2646 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

2643 ms

webpack.runtime.min.js

webpack.runtime.min.js

2903 ms

frontend-modules.min.js

frontend-modules.min.js

3107 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

3158 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

3175 ms

wp-polyfill.min.js

wp-polyfill.min.js

3203 ms

hooks.min.js

hooks.min.js

3184 ms

i18n.min.js

i18n.min.js

3412 ms

frontend.min.js

frontend.min.js

3317 ms

waypoints.min.js

waypoints.min.js

3330 ms

core.min.js

core.min.js

3368 ms

frontend.min.js

frontend.min.js

3366 ms

elements-handlers.min.js

elements-handlers.min.js

3205 ms

jquery.sticky.min.js

jquery.sticky.min.js

3412 ms

logo-eways-01-2.png

logo-eways-01-2.png

2246 ms

D8AED8B1DB8CD8AF-D984D9BE-D8AAD8A7D9BE-D8AFD8A7D986D8B4-D8A2D985D988D8B2DB8C-2-UdFpas-1024x683.jpeg

D8AED8B1DB8CD8AF-D984D9BE-D8AAD8A7D9BE-D8AFD8A7D986D8B4-D8A2D985D988D8B2DB8C-2-UdFpas-1024x683.jpeg

2597 ms

D8AED8B1DB8CD8AF-DAAFD984DAA9D8B3DB8C-D8A8D8A7D8AFD8B2-2-D9BED8B1D988-PLzL9J-1024x683.jpeg

D8AED8B1DB8CD8AF-DAAFD984DAA9D8B3DB8C-D8A8D8A7D8AFD8B2-2-D9BED8B1D988-PLzL9J-1024x683.jpeg

2656 ms

D8A8D987D8A8D988D8AF-D8B9D985D984DAA9D8B1D8AF-D8A8D8A7D8AAD8B1DB8C-DAAFD988D8B4DB8C-2-DhYPX4-1024x683.jpeg

D8A8D987D8A8D988D8AF-D8B9D985D984DAA9D8B1D8AF-D8A8D8A7D8AAD8B1DB8C-DAAFD988D8B4DB8C-2-DhYPX4-1024x683.jpeg

2708 ms

D8A7D986D988D8A7D8B9-D986DAA9D8A7D8AA-D8AED8B1DB8CD8AF-D984D9BE-D8AAD8A7D9BE-6933JO.webp

D8A7D986D988D8A7D8B9-D986DAA9D8A7D8AA-D8AED8B1DB8CD8AF-D984D9BE-D8AAD8A7D9BE-6933JO.webp

2871 ms

D982D8A7D8A8D984DB8CD8AA-D981D986DB8C-D8B3D8A7D8B9D8AA-D987D988D8B4D985D986D8AF-D8B3D8A7D985D8B3D988D986DAAF-SVYfZm-1024x683.webp

D982D8A7D8A8D984DB8CD8AA-D981D986DB8C-D8B3D8A7D8B9D8AA-D987D988D8B4D985D986D8AF-D8B3D8A7D985D8B3D988D986DAAF-SVYfZm-1024x683.webp

2895 ms

logo-eways-2.svg

logo-eways-2.svg

3554 ms

E-Namad.webp

E-Namad.webp

3102 ms

Hero-Eways.svg

Hero-Eways.svg

2997 ms

Eways-6.webp

Eways-6.webp

3253 ms

Eways-7.webp

Eways-7.webp

3366 ms

App-Eways.svg

App-Eways.svg

3238 ms

KalamehWeb-Medium.woff

KalamehWeb-Medium.woff

3347 ms

KalamehWeb-Regular.woff

KalamehWeb-Regular.woff

3763 ms

KalamehWeb-Light.woff

KalamehWeb-Light.woff

3861 ms

KalamehWeb-ExtraLight.woff

KalamehWeb-ExtraLight.woff

4033 ms

KalamehWeb-Thin.woff

KalamehWeb-Thin.woff

4002 ms

KalamehWeb-SemiBold.woff

KalamehWeb-SemiBold.woff

4145 ms

KalamehWeb-Bold.woff

KalamehWeb-Bold.woff

4231 ms

embed

embed

249 ms

KalamehWeb-ExtraBold.woff

KalamehWeb-ExtraBold.woff

4433 ms

KalamehWeb-Black.woff

KalamehWeb-Black.woff

4549 ms

js

js

50 ms

Accessibility Review

eways.ir accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

eways.ir best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

eways.ir SEO score

99

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eways.ir can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Eways.ir main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

eways.ir

Open Graph description is not detected on the main page of Eways. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: