Tools & Wizards About Us
ruban.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ruban.com

روبان | فروشگاه اینترنتی آرایشی بهداشتی مد و زیبایی

Page Load Speed

4.6 sec in total

First Response

837 ms

Resources Loaded

3.6 sec

Page Rendered

78 ms

ruban.com screenshot

About Website

Click here to check amazing Ruban content for Iran. Otherwise, check out these important facts you probably never knew about ruban.com

فروشگاه اینترنتی روبان، فروش آنلاین لوازم آرایشی و بهداشتی اصل از برندهای معتبر با بهترین قیمت. ارسال به سراسر ایران

Visit ruban.com

Key Findings

We analyzed Ruban.com page load time and found that the first response time was 837 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

ruban.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value19.5 s

0/100

25%

SI (Speed Index)

Value20.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value1.873

0/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

ruban.com

837 ms

1.css

841 ms

2.css

632 ms

3.css

633 ms

custom.min.css

849 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 81% of them (26 requests) were addressed to the original Ruban.com, 6% (2 requests) were made to Googletagmanager.com and 6% (2 requests) were made to Van.najva.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ruban.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.9 kB (4%)

Content Size

224.3 kB

After Optimization

215.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ruban.com main page is 224.3 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. CSS take 206.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.0 kB

  • Original 11.1 kB
  • After minification 10.2 kB
  • After compression 3.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 8.0 kB or 72% of the original size.

JavaScript Optimization

-8%

Potential reduce by 557 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 6.6 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

-0%

Potential reduce by 328 B

  • Original 206.0 kB
  • After minification 206.0 kB
  • After compression 205.7 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. Ruban.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (89%)

Requests Now

27

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ruban.com

ruban.com

837 ms

1.css

1.css

841 ms

2.css

2.css

632 ms

3.css

3.css

633 ms

custom.min.css

custom.min.css

849 ms

main.css

main.css

955 ms

fontello-new.css

fontello-new.css

768 ms

fontello.css

fontello.css

1512 ms

fontello-customerclub.css

fontello-customerclub.css

980 ms

style.css

style.css

1543 ms

bootstrap.css

bootstrap.css

1325 ms

all.min.css

all.min.css

1316 ms

app.css

app.css

1926 ms

jquery.min.js

jquery.min.js

1171 ms

select2.min.js

select2.min.js

1283 ms

jquery-autocomplete.js

jquery-autocomplete.js

1373 ms

LP-Index.js

LP-Index.js

1434 ms

deema.main.js

deema.main.js

746 ms

js

js

48 ms

external-sources.js

external-sources.js

1414 ms

siema.min.js

siema.min.js

1463 ms

cupertino-pane.js

cupertino-pane.js

1518 ms

app.js

app.js

2008 ms

app.js

app.js

1551 ms

main.js

main.js

1598 ms

4398821.gif

4398821.gif

172 ms

iranyekanregular.ttf

iranyekanregular.ttf

199 ms

iranyekanbold.ttf

iranyekanbold.ttf

107 ms

gtm.js

gtm.js

105 ms

local-messaging.css

local-messaging.css

99 ms

ruban547-website-12173-52b6abdf-4ca7-43a1-b0cc-21bc5d78b725.js

ruban547-website-12173-52b6abdf-4ca7-43a1-b0cc-21bc5d78b725.js

103 ms

rg.complete.js

rg.complete.js

504 ms

Accessibility Review

ruban.com accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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.

Best Practices

ruban.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ruban.com SEO score

90

Search Engine Optimization Advices

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

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ruban.com 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 Ruban.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

ruban.com

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