Tools & Wizards About Us
yellowfx.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

yellowfx.com

Page Load Speed

9.9 sec in total

First Response

2.7 sec

Resources Loaded

7 sec

Page Rendered

208 ms

yellowfx.com screenshot

About Website

Visit yellowfx.com now to see the best up-to-date Yellowfx content for Iran and also check out these interesting facts you probably never knew about yellowfx.com

Forex forecast and technical analysis from Yellow FX team, a site dedicated to forex technical analysis and forex forecasting.

Visit yellowfx.com

Key Findings

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

Performance Metrics

yellowfx.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,590 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

www.yellowfx.com

2741 ms

css2

44 ms

adsbygoogle.js

84 ms

jquery.min.js

29 ms

api.js

73 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 49% of them (19 requests) were addressed to the original Yellowfx.com, 18% (7 requests) were made to Fonts.gstatic.com and 13% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Yellowfx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.3 kB (37%)

Content Size

884.2 kB

After Optimization

557.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yellowfx.com main page is 884.2 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. 70% of websites need less resources to load. Javascripts take 495.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 148.2 kB

  • Original 177.1 kB
  • After minification 177.0 kB
  • After compression 28.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 148.2 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 1.1 kB

  • Original 187.5 kB
  • After minification 186.4 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. Yellowfx images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 177.0 kB

  • Original 495.1 kB
  • After minification 495.1 kB
  • After compression 318.1 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 177.0 kB or 36% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

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

Requests Now

30

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.yellowfx.com

www.yellowfx.com

2741 ms

css2

css2

44 ms

adsbygoogle.js

adsbygoogle.js

84 ms

jquery.min.js

jquery.min.js

29 ms

api.js

api.js

73 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

22 ms

wp-polyfill.min.js

wp-polyfill.min.js

71 ms

jquery.min.js

jquery.min.js

230 ms

autoptimize_66957d8cb1c2824ce6440ff99350385c.js

autoptimize_66957d8cb1c2824ce6440ff99350385c.js

151 ms

analytics.js

analytics.js

92 ms

forex-ea-forex-signal-developer.gif

forex-ea-forex-signal-developer.gif

85 ms

zigzag-fibo-v1beta-300x174.jpg

zigzag-fibo-v1beta-300x174.jpg

192 ms

macdtrad4-300x174.jpg

macdtrad4-300x174.jpg

192 ms

dayhl-300x174.jpg

dayhl-300x174.jpg

190 ms

supertrend-300x174.jpg

supertrend-300x174.jpg

190 ms

keltner-channels-300x174.jpg

keltner-channels-300x174.jpg

190 ms

excandles-300x174.jpg

excandles-300x174.jpg

190 ms

alert-sma-ema-crossover-300x174.jpg

alert-sma-ema-crossover-300x174.jpg

191 ms

time-to-next-bar-300x174.jpg

time-to-next-bar-300x174.jpg

192 ms

macdonrsi-300x174.jpg

macdonrsi-300x174.jpg

192 ms

fxmfish-1-2.jpg

fxmfish-1-2.jpg

2128 ms

qqe20alert20v3-300x174.jpg

qqe20alert20v3-300x174.jpg

192 ms

macd-crossover-alert-300x174.jpg

macd-crossover-alert-300x174.jpg

193 ms

recaptcha__en.js

recaptcha__en.js

158 ms

collect

collect

118 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

96 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

110 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

122 ms

KFOjCnqEu92Fr1Mu51TjARc9.ttf

KFOjCnqEu92Fr1Mu51TjARc9.ttf

125 ms

anchor

anchor

48 ms

styles__ltr.css

styles__ltr.css

8 ms

recaptcha__en.js

recaptcha__en.js

14 ms

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

tE6BD2dmJ4MsSW_XgLndBgqWpAgx-dXQ3y0tInp2GOI.js

50 ms

webworker.js

webworker.js

46 ms

logo_48.png

logo_48.png

33 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

30 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

29 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

29 ms

recaptcha__en.js

recaptcha__en.js

33 ms

Accessibility Review

yellowfx.com accessibility score

82

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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>).

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

yellowfx.com 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

yellowfx.com SEO score

91

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yellowfx.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Yellowfx.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

yellowfx.com

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