Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

yekta.com

Yekta Persian Market & Kabob Counter

Page Load Speed

16.7 sec in total

First Response

91 ms

Resources Loaded

13.8 sec

Page Rendered

2.8 sec

yekta.com screenshot

About Website

Welcome to yekta.com homepage info - get ready to check Yekta best content right away, or after learning these important things about yekta.com

Yekta Persian Market & Kabob Counter is your ultimate Iranian store and Persian food service. Our online Persian store offer a wide variety of high-quality Iranian and Middle Eastern groceries. Shoppi...

Visit yekta.com

Key Findings

We analyzed Yekta.com page load time and found that the first response time was 91 ms and then it took 16.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

yekta.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value36.7 s

0/100

25%

SI (Speed Index)

Value69.2 s

0/100

10%

TBT (Total Blocking Time)

Value109,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.146

77/100

15%

TTI (Time to Interactive)

Value135.3 s

0/100

10%

Network Requests Diagram

yekta.com

91 ms

yektamarket.com

1364 ms

css2

273 ms

index.css

420 ms

style.min.css

389 ms

Our browser made a total of 193 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yekta.com, 53% (103 requests) were made to Yektamarket.com and 22% (42 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (6.8 sec) relates to the external source Yektamarket.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 538.2 kB (13%)

Content Size

4.2 MB

After Optimization

3.7 MB

In fact, the total size of Yekta.com main page is 4.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 435.7 kB

  • Original 497.5 kB
  • After minification 473.9 kB
  • After compression 61.8 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 435.7 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 6.0 kB

  • Original 3.1 MB
  • After minification 3.1 MB

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. Yekta images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 242.8 kB
  • After minification 242.8 kB
  • After compression 239.4 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

-26%

Potential reduce by 93.1 kB

  • Original 364.9 kB
  • After minification 364.0 kB
  • After compression 271.8 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. Yekta.com needs all CSS files to be minified and compressed as it can save up to 93.1 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 118 (65%)

Requests Now

182

After Optimization

64

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

Accessibility Review

yekta.com accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

yekta.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yekta.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Yekta.com 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

Open Graph data is detected on the main page of Yekta. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: