Tools & Wizards About Us
olink.ir screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

olink.ir

ترجمه انگلیسی و فارسی قلم طلایی

Page Load Speed

24.2 sec in total

First Response

384 ms

Resources Loaded

22.4 sec

Page Rendered

1.4 sec

olink.ir screenshot

About Website

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

جهت دریافت ترجمه تخصصی انگلیسی به فارسی و فارسی به انگلیسی کلیک نمایید. هزینه ترجمه بسیار مناسب بوده و کیفیت ترجمه به صورت کامل تضمین شده است.

Visit olink.ir

Key Findings

We analyzed Olink.ir page load time and found that the first response time was 384 ms and then it took 23.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

olink.ir performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.351

31/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

olink.ir

384 ms

www.olink.ir

843 ms

autoptimize_b4ef5ecf0c760ca7113f59b86e5c66ed.css

97 ms

autoptimize_a1baa942ea06f0d65ea250a2f9e76185.css

289 ms

css

32 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 62% of them (21 requests) were addressed to the original Olink.ir, 18% (6 requests) were made to Apis.google.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Trustseal.enamad.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.6 kB (22%)

Content Size

711.3 kB

After Optimization

552.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Olink.ir main page is 711.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. 35% of websites need less resources to load. Javascripts take 311.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 39.6 kB

  • Original 51.6 kB
  • After minification 50.8 kB
  • After compression 12.0 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 39.6 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 243 B

  • Original 218.6 kB
  • After minification 218.3 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. Olink images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 112.3 kB

  • Original 311.7 kB
  • After minification 311.7 kB
  • After compression 199.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 112.3 kB or 36% of the original size.

CSS Optimization

-5%

Potential reduce by 6.4 kB

  • Original 129.5 kB
  • After minification 129.5 kB
  • After compression 123.1 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. Olink.ir has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

olink.ir

olink.ir

384 ms

www.olink.ir

www.olink.ir

843 ms

autoptimize_b4ef5ecf0c760ca7113f59b86e5c66ed.css

autoptimize_b4ef5ecf0c760ca7113f59b86e5c66ed.css

97 ms

autoptimize_a1baa942ea06f0d65ea250a2f9e76185.css

autoptimize_a1baa942ea06f0d65ea250a2f9e76185.css

289 ms

css

css

32 ms

jquery.min.js

jquery.min.js

382 ms

autoptimize_3d8535d7a9379a4e0be5aee21d12bc43.js

autoptimize_3d8535d7a9379a4e0be5aee21d12bc43.js

469 ms

logo.aspx

logo.aspx

20106 ms

logo.aspx

logo.aspx

529 ms

noise.png

noise.png

121 ms

header1.png

header1.png

121 ms

header2.png

header2.png

299 ms

persian-translation-and-english-translation.png

persian-translation-and-english-translation.png

120 ms

online_translation_gp.png

online_translation_gp.png

207 ms

online-translator-persian-and-english.png

online-translator-persian-and-english.png

206 ms

olink_translation_persian_english1.png

olink_translation_persian_english1.png

206 ms

side1.png

side1.png

299 ms

side-5.png

side-5.png

300 ms

side-7.png

side-7.png

300 ms

side2.png

side2.png

301 ms

side-4.png

side-4.png

301 ms

side-6.png

side-6.png

391 ms

plusone.js

plusone.js

59 ms

wAAAAAAAHicY2BgYGQAgisqM9VA9LaKV5FQOg8AQTAGsAA=

wAAAAAAAHicY2BgYGQAgisqM9VA9LaKV5FQOg8AQTAGsAA=

1 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

32 ms

fastbutton

fastbutton

44 ms

postmessageRelay

postmessageRelay

35 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

25 ms

rpc:shindig_random.js

rpc:shindig_random.js

8 ms

developers.google.com

developers.google.com

282 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

autoptimize_c541e051c48f89181bd3deadc2b61a80.css

autoptimize_c541e051c48f89181bd3deadc2b61a80.css

98 ms

autoptimize_0af3605f23e3b397fb668fa58de5d763.css

autoptimize_0af3605f23e3b397fb668fa58de5d763.css

96 ms

Accessibility Review

olink.ir accessibility score

86

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

olink.ir best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

olink.ir SEO score

84

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 doesn't use 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 Olink.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 Olink.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

olink.ir

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