Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

fxrec.com

FX[ユーロドル]チャート記録|羊飼いのFX記録室

Page Load Speed

7 sec in total

First Response

645 ms

Resources Loaded

5.5 sec

Page Rendered

854 ms

fxrec.com screenshot

About Website

Welcome to fxrec.com homepage info - get ready to check FX Rec best content for Japan right away, or after learning these important things about fxrec.com

羊飼いがFXチャートを記録&取引システムを徹底調査!各為替チャート記録ではGFTまたはIG証券のものを正式に許可を得て使用・掲載!トレードするにあたって非常に重要かつ実用的なデータをまとめました!

Visit fxrec.com

Key Findings

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

Performance Metrics

fxrec.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

fxrec.com

645 ms

fxrec.com

1066 ms

style.css

210 ms

base.css

420 ms

menu.css

533 ms

Our browser made a total of 136 requests to load all elements on the main page. We found that 29% of them (39 requests) were addressed to the original Fxrec.com, 30% (41 requests) were made to Fxforexing.com and 10% (13 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Fxforexing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 499.2 kB (32%)

Content Size

1.6 MB

After Optimization

1.1 MB

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

HTML Optimization

-88%

Potential reduce by 149.3 kB

  • Original 170.5 kB
  • After minification 145.8 kB
  • After compression 21.2 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. This page needs HTML code to be minified as it can gain 24.7 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 149.3 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 31.1 kB

  • Original 621.4 kB
  • After minification 590.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. FX Rec images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 310.1 kB

  • Original 747.0 kB
  • After minification 745.7 kB
  • After compression 436.9 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 310.1 kB or 42% of the original size.

CSS Optimization

-63%

Potential reduce by 8.8 kB

  • Original 14.0 kB
  • After minification 10.4 kB
  • After compression 5.2 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. Fxrec.com needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 50 (39%)

Requests Now

128

After Optimization

78

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

Accessibility Review

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

fxrec.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fxrec.com SEO score

67

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fxrec.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fxrec.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 FX Rec. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: