Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

forex.pm

forex forum binary options trade - Index

Page Load Speed

22 sec in total

First Response

446 ms

Resources Loaded

20.4 sec

Page Rendered

1.2 sec

forex.pm screenshot

About Website

Visit forex.pm now to see the best up-to-date Forex content for United States and also check out these interesting facts you probably never knew about forex.pm

forex forum binary options trade - Index

Visit forex.pm

Key Findings

We analyzed Forex.pm page load time and found that the first response time was 446 ms and then it took 21.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

forex.pm performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value7.9 s

44/100

10%

Network Requests Diagram

forex.pm

446 ms

23087e0412d3g6a3c8.jpg

849 ms

iqoption

32 ms

minified_9fb185eb3dbe92ad2e698eced23a5834.css

374 ms

jquery.min.js

85 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 18% of them (7 requests) were addressed to the original Forex.pm, 8% (3 requests) were made to Static.cdnpub.info and 8% (3 requests) were made to Betiforex.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Ads.pipaffiliates.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.6 kB (8%)

Content Size

1.4 MB

After Optimization

1.3 MB

In fact, the total size of Forex.pm main page is 1.4 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 70.2 kB

  • Original 86.1 kB
  • After minification 78.0 kB
  • After compression 16.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 70.2 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 36.1 kB

  • Original 1.2 MB
  • After minification 1.2 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. Forex images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 5.3 kB

  • Original 54.7 kB
  • After minification 52.3 kB
  • After compression 49.3 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 57 B

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 23.0 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. Forex.pm has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (10%)

Requests Now

31

After Optimization

28

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

Accessibility Review

forex.pm accessibility score

75

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

forex.pm best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

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

forex.pm SEO score

54

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

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 Forex.pm 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 Forex.pm 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 Forex. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: