Tools & Wizards About Us
currencyapi.net screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

currencyapi.net

Real-time currency exchange for developers - CurrencyApi

Page Load Speed

2 sec in total

First Response

88 ms

Resources Loaded

953 ms

Page Rendered

996 ms

currencyapi.net screenshot

About Website

Click here to check amazing Currency Api content. Otherwise, check out these important facts you probably never knew about currencyapi.net

Free currency feed for over 152 currencies including cryptos, like Bitcoin, Litecoin and Ethereum. JSON and XML currency api updated every 60 seconds.

Visit currencyapi.net

Key Findings

We analyzed Currencyapi.net page load time and found that the first response time was 88 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

currencyapi.net performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value2,630 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value12.7 s

13/100

10%

Network Requests Diagram

currencyapi.net

88 ms

currencyapi.net

195 ms

gtm.js

122 ms

app.css

42 ms

TNP41379UC01TG0ZLTB9.js

283 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 89% of them (34 requests) were addressed to the original Currencyapi.net, 5% (2 requests) were made to Static.small.chat and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (283 ms) relates to the external source Embed.small.chat.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.6 kB (49%)

Content Size

754.2 kB

After Optimization

385.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Currencyapi.net main page is 754.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. HTML takes 572.0 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 347.0 kB

  • Original 572.0 kB
  • After minification 551.3 kB
  • After compression 224.9 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 347.0 kB or 61% of the original size.

Image Optimization

-23%

Potential reduce by 17.2 kB

  • Original 73.9 kB
  • After minification 56.7 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. Obviously, Currency Api needs image optimization as it can save up to 17.2 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

-0%

Potential reduce by 0 B

  • Original 88.5 kB
  • After minification 88.5 kB
  • After compression 88.5 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

-22%

Potential reduce by 4.4 kB

  • Original 19.8 kB
  • After minification 19.8 kB
  • After compression 15.4 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. Currencyapi.net needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (33%)

Requests Now

33

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

currencyapi.net

currencyapi.net

88 ms

currencyapi.net

currencyapi.net

195 ms

gtm.js

gtm.js

122 ms

app.css

app.css

42 ms

TNP41379UC01TG0ZLTB9.js

TNP41379UC01TG0ZLTB9.js

283 ms

homepage.js

homepage.js

87 ms

hero-bg.webp

hero-bg.webp

44 ms

i.png

i.png

43 ms

a.png

a.png

73 ms

sk.png

sk.png

72 ms

sv.png

sv.png

80 ms

h.png

h.png

73 ms

how-to-get-live-currency-rates.webp

how-to-get-live-currency-rates.webp

56 ms

usd.svg

usd.svg

69 ms

eur.svg

eur.svg

76 ms

gbp.svg

gbp.svg

73 ms

jpy.svg

jpy.svg

80 ms

aud.svg

aud.svg

83 ms

cad.svg

cad.svg

82 ms

chf.svg

chf.svg

85 ms

cny.svg

cny.svg

88 ms

inr.svg

inr.svg

105 ms

brl.svg

brl.svg

108 ms

btc.svg

btc.svg

102 ms

eth.svg

eth.svg

99 ms

ltc.svg

ltc.svg

105 ms

xrp.svg

xrp.svg

110 ms

bch.svg

bch.svg

119 ms

xau.svg

xau.svg

113 ms

xag.svg

xag.svg

114 ms

other.svg

other.svg

116 ms

oliver-lynch.jpg

oliver-lynch.jpg

120 ms

afaan-ashiq.jpg

afaan-ashiq.jpg

116 ms

peter-dudbridge.jpg

peter-dudbridge.jpg

121 ms

fa-solid-900.woff

fa-solid-900.woff

47 ms

fa-regular-400.woff

fa-regular-400.woff

33 ms

messenger.css

messenger.css

59 ms

messenger.js

messenger.js

86 ms

Accessibility Review

currencyapi.net accessibility score

87

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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.

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

currencyapi.net 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

High

Missing source maps for large first-party JavaScript

SEO Factors

currencyapi.net SEO score

100

Search Engine Optimization Advices

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 Currencyapi.net 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 Currencyapi.net 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

currencyapi.net

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