Tools & Wizards About Us
lbma-i.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

lbma-i.com

LBMA Trade Data - Precious Metals Market | Nasdaq

Page Load Speed

5 sec in total

First Response

399 ms

Resources Loaded

3.7 sec

Page Rendered

939 ms

lbma-i.com screenshot

About Website

Welcome to lbma-i.com homepage info - get ready to check LBMA I best content right away, or after learning these important things about lbma-i.com

View LBMA's OTC trade market data on Nasdaq to learn more about the precious metals market includes Loco London and Loco Zurich standards.

Visit lbma-i.com

Key Findings

We analyzed Lbma-i.com page load time and found that the first response time was 399 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

lbma-i.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

lbma-i

399 ms

LBMA-Trade-Data

2435 ms

google_tag.script.js

69 ms

css_YQayzHFXFzyRQXVMUVf41KfZdvA1jOkDEbI9OfGCD0s.css

27 ms

css_tNrY3X3WbtRkagjDuLNZEzCio3qfL-hHfFMkoJtXh6I.css

35 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Lbma-i.com, 9% (4 requests) were made to Cdn.cookielaw.org and 2% (1 request) were made to Cdn.jwplayer.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Nasdaq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 958.0 kB (27%)

Content Size

3.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lbma-i.com main page is 3.5 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. 75% 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 140.8 kB

  • Original 168.4 kB
  • After minification 137.4 kB
  • After compression 27.6 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 31.0 kB, which is 18% 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 140.8 kB or 84% of the original size.

Image Optimization

-23%

Potential reduce by 606.8 kB

  • Original 2.7 MB
  • After minification 2.1 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. Obviously, LBMA I needs image optimization as it can save up to 606.8 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-33%

Potential reduce by 187.1 kB

  • Original 560.1 kB
  • After minification 560.1 kB
  • After compression 373.0 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 187.1 kB or 33% of the original size.

CSS Optimization

-28%

Potential reduce by 23.2 kB

  • Original 82.5 kB
  • After minification 82.0 kB
  • After compression 59.3 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. Lbma-i.com needs all CSS files to be minified and compressed as it can save up to 23.2 kB or 28% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LBMA I. 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

lbma-i

lbma-i

399 ms

LBMA-Trade-Data

LBMA-Trade-Data

2435 ms

google_tag.script.js

google_tag.script.js

69 ms

css_YQayzHFXFzyRQXVMUVf41KfZdvA1jOkDEbI9OfGCD0s.css

css_YQayzHFXFzyRQXVMUVf41KfZdvA1jOkDEbI9OfGCD0s.css

27 ms

css_tNrY3X3WbtRkagjDuLNZEzCio3qfL-hHfFMkoJtXh6I.css

css_tNrY3X3WbtRkagjDuLNZEzCio3qfL-hHfFMkoJtXh6I.css

35 ms

SWBnp2Tm.js

SWBnp2Tm.js

30 ms

tcf.stub.js

tcf.stub.js

66 ms

otSDKStub.js

otSDKStub.js

77 ms

bizible.js

bizible.js

355 ms

1785586d

1785586d

65 ms

js_ybxzah74FYByexWgiMLGpd5zeZ7_F9Y9suRsE0ChiMs.js

js_ybxzah74FYByexWgiMLGpd5zeZ7_F9Y9suRsE0ChiMs.js

66 ms

eu_cookie_compliance.min.js

eu_cookie_compliance.min.js

26 ms

js_wBO7rfLMtqQ-dVpET6pARupaFigwbVxcoCdkWs1h7N4.js

js_wBO7rfLMtqQ-dVpET6pARupaFigwbVxcoCdkWs1h7N4.js

73 ms

forms2.min.js

forms2.min.js

77 ms

p.css

p.css

51 ms

578a06dd-f15c-46aa-8b1d-7dfe08fd6747.json

578a06dd-f15c-46aa-8b1d-7dfe08fd6747.json

247 ms

Header%20-%20AdobeStock_121313488.jpeg

Header%20-%20AdobeStock_121313488.jpeg

238 ms

gtm.js

gtm.js

387 ms

nasdaq-plus.svg

nasdaq-plus.svg

89 ms

gold35.jpg

gold35.jpg

91 ms

wealth-icon.png

wealth-icon.png

87 ms

Refinitiv%20logo.png

Refinitiv%20logo.png

89 ms

bloomberg.png

bloomberg.png

90 ms

Trade%20Data%2012.02.24.png

Trade%20Data%2012.02.24.png

107 ms

AdobeStock_197237637.jpeg

AdobeStock_197237637.jpeg

98 ms

NTS%20Energy%20Utilities.png

NTS%20Energy%20Utilities.png

95 ms

video-icon.svg

video-icon.svg

96 ms

ziLDZedA.jpg

ziLDZedA.jpg

96 ms

bVHiT9Nw.jpg

bVHiT9Nw.jpg

95 ms

ZmFyLYUd.jpg

ZmFyLYUd.jpg

112 ms

egMdjepD.jpg

egMdjepD.jpg

109 ms

logo-lbma.jpg

logo-lbma.jpg

109 ms

0380-Q20%20LBMA-i%20graphic_CS_v1.png

0380-Q20%20LBMA-i%20graphic_CS_v1.png

109 ms

AdobeStock_48286460_vertical.jpg

AdobeStock_48286460_vertical.jpg

112 ms

location

location

64 ms

Roboto-Regular.woff

Roboto-Regular.woff

33 ms

sourcesanspro-semibold-webfont.woff

sourcesanspro-semibold-webfont.woff

31 ms

nasdaq-icons.ttf

nasdaq-icons.ttf

23 ms

nasdaq-icons.ttf

nasdaq-icons.ttf

33 ms

sourcesanspro-regular-webfont.woff

sourcesanspro-regular-webfont.woff

56 ms

www.nasdaq.com

www.nasdaq.com

24 ms

otBannerSdk.js

otBannerSdk.js

20 ms

nasdaq-icons.woff

nasdaq-icons.woff

16 ms

www.nasdaq.com

www.nasdaq.com

15 ms

nasdaq-icons.svg

nasdaq-icons.svg

10 ms

www.nasdaq.com

www.nasdaq.com

11 ms

Accessibility Review

lbma-i.com accessibility score

74

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes are not valid or misspelled

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

lbma-i.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

SEO Factors

lbma-i.com 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

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

High

Tap targets are not sized appropriately

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 Lbma-i.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 Lbma-i.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

lbma-i.com

Open Graph description is not detected on the main page of LBMA I. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: