Tools & Wizards About Us
firstcall.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

firstcall.com

LSEG Data & Analytics | Financial Technology & Data | LSEG

Page Load Speed

2.4 sec in total

First Response

161 ms

Resources Loaded

1.6 sec

Page Rendered

652 ms

firstcall.com screenshot

About Website

Welcome to firstcall.com homepage info - get ready to check Firstcall best content right away, or after learning these important things about firstcall.com

LSEG Data & Analytics: Partnering with 40,000+ customers and 400,000+ users worldwide to empower financial insights through data and technology.

Visit firstcall.com

Key Findings

We analyzed Firstcall.com page load time and found that the first response time was 161 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

firstcall.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value23.0 s

1/100

10%

Network Requests Diagram

firstcall.com

161 ms

114 ms

35 ms

main.css

32 ms

jquery.min.js

14 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Firstcall.com, 56% (57 requests) were made to Lseg.com and 15% (15 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (973 ms) relates to the external source Lseg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (37%)

Content Size

3.7 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Firstcall.com main page is 3.7 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 340.9 kB

  • Original 388.5 kB
  • After minification 325.5 kB
  • After compression 47.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 63.0 kB, which is 16% 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 340.9 kB or 88% of the original size.

Image Optimization

-22%

Potential reduce by 466.1 kB

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

JavaScript Optimization

-51%

Potential reduce by 578.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 565.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 578.7 kB or 51% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 57 (65%)

Requests Now

88

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

firstcall.com

firstcall.com

161 ms

114 ms

35 ms

main.css

main.css

32 ms

jquery.min.js

jquery.min.js

14 ms

clientlibs.min.js

clientlibs.min.js

17 ms

clientlibs.min.css

clientlibs.min.css

18 ms

launch-EN115a9a0ff4754e369c3264131cc84b57.min.js

launch-EN115a9a0ff4754e369c3264131cc84b57.min.js

29 ms

clientlibs.min.js

clientlibs.min.js

17 ms

clientlibs.min.js

clientlibs.min.js

18 ms

clientlibs_common.min.css

clientlibs_common.min.css

18 ms

clientlibs_kaltura_player.min.css

clientlibs_kaltura_player.min.css

24 ms

clientlibs_kaltura_player.min.js

clientlibs_kaltura_player.min.js

23 ms

2479521

2479521

184 ms

clientlibs_common.min.css

clientlibs_common.min.css

23 ms

csrf.min.js

csrf.min.js

22 ms

clientlibs_common.min.css

clientlibs_common.min.css

22 ms

clientlibs.min.js

clientlibs.min.js

24 ms

main.js

main.js

156 ms

lseg-data-analytics-logo.svg

lseg-data-analytics-logo.svg

207 ms

image.jpg

image.jpg

205 ms

image.jpg

image.jpg

205 ms

image.jpg

image.jpg

260 ms

data-analytics-hero.png

data-analytics-hero.png

271 ms

image.png

image.png

271 ms

image.png

image.png

306 ms

image.png

image.png

275 ms

image.png

image.png

289 ms

image.jpg

image.jpg

275 ms

image.jpg

image.jpg

287 ms

image.jpg

image.jpg

290 ms

image.jpg

image.jpg

290 ms

image.jpg

image.jpg

286 ms

time-07.svg

time-07.svg

308 ms

image.jpg

image.jpg

312 ms

image.jpg

image.jpg

311 ms

logo-white-v2.svg

logo-white-v2.svg

309 ms

AppMeasurement.min.js

AppMeasurement.min.js

68 ms

AppMeasurement_Module_AudienceManagement.min.js

AppMeasurement_Module_AudienceManagement.min.js

217 ms

js

js

235 ms

analytics.js

analytics.js

223 ms

ip.json

ip.json

227 ms

otSDKStub.js

otSDKStub.js

228 ms

iframe_api

iframe_api

221 ms

proximanova-regular-webfont.woff

proximanova-regular-webfont.woff

593 ms

proximanova-medium-webfont.woff

proximanova-medium-webfont.woff

608 ms

proximanova-light-webfont.woff

proximanova-light-webfont.woff

606 ms

proximanova-semibold-webfont.woff

proximanova-semibold-webfont.woff

592 ms

proximanova-bold-webfont.woff

proximanova-bold-webfont.woff

596 ms

lseg_motto_medium.woff

lseg_motto_medium.woff

595 ms

lseg_motto_regular.woff

lseg_motto_regular.woff

924 ms

lseg_motto_light.woff

lseg_motto_light.woff

924 ms

lseg_motto_semibold.woff

lseg_motto_semibold.woff

958 ms

lseg_motto_bold.woff

lseg_motto_bold.woff

922 ms

token.json

token.json

774 ms

23.js

23.js

512 ms

53.js

53.js

512 ms

3.js

3.js

512 ms

4.js

4.js

513 ms

8.js

8.js

558 ms

42.js

42.js

559 ms

17.js

17.js

559 ms

33.js

33.js

557 ms

lda3246158-lseg-analytics-hero-1440x355-v2.jpg

lda3246158-lseg-analytics-hero-1440x355-v2.jpg

973 ms

RCa60c3bbeb62a4e4db011aa00acf7fb50-source.min.js

RCa60c3bbeb62a4e4db011aa00acf7fb50-source.min.js

33 ms

RC4d454a8fd21b4dc8b41954a71a3a9fea-source.min.js

RC4d454a8fd21b4dc8b41954a71a3a9fea-source.min.js

60 ms

RC234fd126c802403db8ef3c2848a98ddf-source.min.js

RC234fd126c802403db8ef3c2848a98ddf-source.min.js

42 ms

RCf13cfcbc8c224b49b97bfbc4b633b1f0-source.min.js

RCf13cfcbc8c224b49b97bfbc4b633b1f0-source.min.js

44 ms

RC572b114c42834c97a48494de049ec33e-source.min.js

RC572b114c42834c97a48494de049ec33e-source.min.js

60 ms

RC32ef8f41d108422cae193c794dde52e8-source.min.js

RC32ef8f41d108422cae193c794dde52e8-source.min.js

60 ms

RCefa4d2e0589347b7b93735174d6e1e1f-source.min.js

RCefa4d2e0589347b7b93735174d6e1e1f-source.min.js

59 ms

RC013db61383594744b3b7618e66c1bd16-source.min.js

RC013db61383594744b3b7618e66c1bd16-source.min.js

58 ms

RCdd30002989264af6a6656d1caf29214e-source.min.js

RCdd30002989264af6a6656d1caf29214e-source.min.js

58 ms

www-widgetapi.js

www-widgetapi.js

8 ms

d040b48c-211e-47e7-8532-2f1dd92e9de2.json

d040b48c-211e-47e7-8532-2f1dd92e9de2.json

90 ms

js

js

34 ms

activityi;src=10631284;type=ros9w0;cat=lseg-0;ord=1;num=1026668787654;npa=0;auiddc=1474990897.1715977189;pscdl=noapi;frm=0;gtm=45fe45f0v9167678111za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.lseg.com%2Fen%2Fdata-analytics%2F

activityi;src=10631284;type=ros9w0;cat=lseg-0;ord=1;num=1026668787654;npa=0;auiddc=1474990897.1715977189;pscdl=noapi;frm=0;gtm=45fe45f0v9167678111za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.lseg.com%2Fen%2Fdata-analytics%2F

104 ms

location

location

53 ms

delivery

delivery

470 ms

otBannerSdk.js

otBannerSdk.js

29 ms

a4ccf60dff7fe1ae.min.js

a4ccf60dff7fe1ae.min.js

14 ms

sync

sync

33 ms

en.json

en.json

31 ms

src=10631284;type=ros9w0;cat=lseg-0;ord=1;num=1026668787654;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe45f0v9167678111za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.lseg.com%2Fen%2Fdata-analytics%2F

src=10631284;type=ros9w0;cat=lseg-0;ord=1;num=1026668787654;npa=0;auiddc=*;pscdl=noapi;frm=0;gtm=45fe45f0v9167678111za200;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.lseg.com%2Fen%2Fdata-analytics%2F

177 ms

sync

sync

44 ms

tap.php

tap.php

49 ms

ip.json

ip.json

165 ms

otFlat.json

otFlat.json

24 ms

otPcCenter.json

otPcCenter.json

19 ms

otCommonStyles.css

otCommonStyles.css

23 ms

rum

rum

108 ms

ot_close.svg

ot_close.svg

58 ms

MicrosoftTeams-image_(1).png

MicrosoftTeams-image_(1).png

48 ms

log

log

217 ms

0.js

0.js

43 ms

1.js

1.js

47 ms

6.js

6.js

8 ms

10.js

10.js

11 ms

RC5057447de23a4e0fa6e0d97ffdf78649-source.min.js

RC5057447de23a4e0fa6e0d97ffdf78649-source.min.js

32 ms

RCba96e6bebe64485da608936ea3270212-source.min.js

RCba96e6bebe64485da608936ea3270212-source.min.js

30 ms

RCf3ca10fa5eb4433398a3d96c92ab9bd5-source.min.js

RCf3ca10fa5eb4433398a3d96c92ab9bd5-source.min.js

29 ms

Accessibility Review

firstcall.com accessibility score

96

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-hidden="true"] elements contain focusable descendents

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.

Best Practices

firstcall.com best practices score

83

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

Browser errors were logged to the console

SEO Factors

firstcall.com SEO score

93

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

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

firstcall.com

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