Tools & Wizards About Us
fgmr.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fgmr.com

James Turk Blog | Free Gold Money Report

Page Load Speed

5.4 sec in total

First Response

116 ms

Resources Loaded

2.4 sec

Page Rendered

2.9 sec

fgmr.com screenshot

About Website

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

Free Gold Money Report aims to help readers better understand gold, money and currency through James Turk’s commentaries and insights.

Visit fgmr.com

Key Findings

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

Performance Metrics

fgmr.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value3,810 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

fgmr.com

116 ms

www.fgmr.com

1251 ms

html5.js

79 ms

css3-mediaqueries.js

80 ms

dashicons.min.css

100 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 73% of them (66 requests) were addressed to the original Fgmr.com, 17% (15 requests) were made to Fonts.gstatic.com and 8% (7 requests) were made to Liveprices.bitgold.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fgmr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (38%)

Content Size

3.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Fgmr.com main page is 3.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 108.9 kB

  • Original 129.2 kB
  • After minification 122.9 kB
  • After compression 20.3 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 108.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 82.1 kB

  • Original 1.9 MB
  • After minification 1.8 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. Fgmr images are well optimized though.

CSS Optimization

-87%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 947.9 kB
  • After compression 154.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. Fgmr.com needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (64%)

Requests Now

70

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fgmr.com

fgmr.com

116 ms

www.fgmr.com

www.fgmr.com

1251 ms

html5.js

html5.js

79 ms

css3-mediaqueries.js

css3-mediaqueries.js

80 ms

dashicons.min.css

dashicons.min.css

100 ms

jquery-ui-dialog.min.css

jquery-ui-dialog.min.css

146 ms

layerslider.css

layerslider.css

159 ms

css

css

120 ms

styles.css

styles.css

70 ms

settings.css

settings.css

94 ms

style.css

style.css

98 ms

style_end.css

style_end.css

123 ms

css

css

143 ms

media-queries_wide.css

media-queries_wide.css

119 ms

rgs.css

rgs.css

141 ms

animations.css

animations.css

146 ms

flexslider.css

flexslider.css

146 ms

font-awesome.css

font-awesome.css

142 ms

moon.css

moon.css

154 ms

elegant.css

elegant.css

149 ms

prettyPhoto.css

prettyPhoto.css

173 ms

thefox_js_composer.css

thefox_js_composer.css

164 ms

zilla-likes.css

zilla-likes.css

158 ms

form-themes.min.css

form-themes.min.css

149 ms

jquery.js

jquery.js

157 ms

jquery-migrate.min.js

jquery-migrate.min.js

157 ms

greensock.js

greensock.js

192 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

212 ms

layerslider.transitions.js

layerslider.transitions.js

170 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

240 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

211 ms

xau.js

xau.js

48 ms

core.min.js

core.min.js

191 ms

widget.min.js

widget.min.js

192 ms

mouse.min.js

mouse.min.js

191 ms

resizable.min.js

resizable.min.js

220 ms

draggable.min.js

draggable.min.js

235 ms

button.min.js

button.min.js

236 ms

position.min.js

position.min.js

235 ms

dialog.min.js

dialog.min.js

238 ms

wpdialog.min.js

wpdialog.min.js

219 ms

customjs.js

customjs.js

226 ms

custom_woo_js.js

custom_woo_js.js

176 ms

smoothscroll.js

smoothscroll.js

176 ms

jquery.form.min.js

jquery.form.min.js

168 ms

scripts.js

scripts.js

170 ms

wp-embed.min.js

wp-embed.min.js

150 ms

forms-api.min.js

forms-api.min.js

151 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

153 ms

FGMR-dark-1.png

FGMR-dark-1.png

51 ms

hyperinflation-1200x565.jpg

hyperinflation-1200x565.jpg

53 ms

silver_bullion-1200x565.jpg

silver_bullion-1200x565.jpg

61 ms

gold_backwardation-1200x565.jpg

gold_backwardation-1200x565.jpg

59 ms

finance-1200x565.jpg

finance-1200x565.jpg

53 ms

shutterstock_330863699-1200x565.jpg

shutterstock_330863699-1200x565.jpg

50 ms

gold_demand-1200x565.jpg

gold_demand-1200x565.jpg

52 ms

rsz_dollar_hyperinflation-1200x565.jpg

rsz_dollar_hyperinflation-1200x565.jpg

55 ms

euro_currency-1200x565.jpg

euro_currency-1200x565.jpg

53 ms

inflation_currency-1200x565.jpg

inflation_currency-1200x565.jpg

53 ms

grexit-1200x565.jpg

grexit-1200x565.jpg

56 ms

james_turk_blog.png

james_turk_blog.png

55 ms

goldmoney-270x270.png

goldmoney-270x270.png

59 ms

hyperinflation-200x160.jpg

hyperinflation-200x160.jpg

53 ms

silver_bullion-200x160.jpg

silver_bullion-200x160.jpg

55 ms

gold_backwardation-200x160.jpg

gold_backwardation-200x160.jpg

56 ms

FGMR-dark-1-300x97.png

FGMR-dark-1-300x97.png

775 ms

hyperinflation-570x570.jpg

hyperinflation-570x570.jpg

81 ms

silver_bullion-570x570.jpg

silver_bullion-570x570.jpg

57 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

396 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

397 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

462 ms

BTu4SsVveqk58cdYjlaM9g.ttf

BTu4SsVveqk58cdYjlaM9g.ttf

497 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

497 ms

vDvcuXwZxUMLuTfuLrSLpA.ttf

vDvcuXwZxUMLuTfuLrSLpA.ttf

538 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

496 ms

zpv3sOKAbMf4wff105oLjw.ttf

zpv3sOKAbMf4wff105oLjw.ttf

537 ms

4cKlrioa77J2iqTqBgkRWg.ttf

4cKlrioa77J2iqTqBgkRWg.ttf

494 ms

5pEc4QKTMA2oB4Hi9NkS4w.ttf

5pEc4QKTMA2oB4Hi9NkS4w.ttf

497 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

21 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

497 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

537 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

537 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

537 ms

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf

539 ms

widget.html

widget.html

296 ms

static

static

98 ms

main.css

main.css

48 ms

us.png

us.png

47 ms

eu.png

eu.png

47 ms

cn.png

cn.png

48 ms

Accessibility Review

fgmr.com accessibility score

83

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.

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

Links do not have a discernible name

High

<object> elements do not have alternate text

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

fgmr.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

fgmr.com SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

fgmr.com

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