4.7 sec in total
389 ms
3.9 sec
360 ms
Visit currencylayer.com now to see the best up-to-date Currency Layer content for Thailand and also check out these interesting facts you probably never knew about currencylayer.com
Free and startup-friendly currency converter JSON API for real-time and historical exchange rates - reliable and accurate, supporting 168 world currencies.
Visit currencylayer.comWe analyzed Currencylayer.com page load time and found that the first response time was 389 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
currencylayer.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.8 s
84/100
25%
Value2.7 s
96/100
10%
Value160 ms
94/100
30%
Value0.016
100/100
15%
Value10.5 s
24/100
10%
389 ms
312 ms
339 ms
232 ms
80 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 76% of them (76 requests) were addressed to the original Currencylayer.com, 7% (7 requests) were made to Apis.google.com and 2% (2 requests) were made to Google-code-prettify.googlecode.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Currencylayer.com.
Page size can be reduced by 306.0 kB (51%)
595.0 kB
289.0 kB
In fact, the total size of Currencylayer.com main page is 595.0 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. 50% of websites need less resources to load. Images take 215.9 kB which makes up the majority of the site volume.
Potential reduce by 50.7 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 17.3 kB, which is 29% 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 50.7 kB or 83% of the original size.
Potential reduce by 33.9 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 Layer needs image optimization as it can save up to 33.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 105.3 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 105.3 kB or 60% of the original size.
Potential reduce by 116.1 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. Currencylayer.com needs all CSS files to be minified and compressed as it can save up to 116.1 kB or 81% of the original size.
Number of requests can be reduced by 26 (27%)
97
71
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Currency Layer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
currencylayer.com
389 ms
jquery.min.js
312 ms
shared.css
339 ms
currencylayer_main.css
232 ms
run_prettify.js
80 ms
prettify.css
230 ms
css
67 ms
jquery.panelSnap.js
235 ms
platform.js
62 ms
getgeotrustsslseal
77 ms
tipr.min.js
233 ms
jquery.md5.js
502 ms
jquery.countTo.js
599 ms
index_script.js
597 ms
respond.min.js
600 ms
scripts.js
596 ms
main.js
662 ms
prettify.css
18 ms
currencylayer_header.png
466 ms
currencylayer_header_x2.png
481 ms
power_plug_round_x2.png
480 ms
compatible_x2.png
481 ms
scroll_arrow_x2.png
583 ms
scroll_arrow_up_x2.png
583 ms
pixar.png
705 ms
pixar_x2.png
715 ms
griffin2.png
721 ms
griffin2_x2.png
721 ms
fedex.png
782 ms
fedex_x2.png
797 ms
ncr.png
934 ms
ncr_x2.png
933 ms
metlife.png
951 ms
metlife_x2.png
952 ms
zoopla.png
1001 ms
zoopla_x2.png
1097 ms
lyft.png
1162 ms
lyft_x2.png
1164 ms
currencylayer_popup.png
1172 ms
currencylayer_popup_x2.png
1176 ms
apilayer_151.png
1220 ms
apilayer_300.png
1317 ms
sdk.js
567 ms
world-dots.png
1436 ms
symbol_USD.png
1370 ms
symbol_BTC.png
1374 ms
symbol_BRL.png
1380 ms
symbol_CHF.png
1433 ms
symbol_CZK.png
1522 ms
widgets.js
284 ms
github-btn.html
88 ms
getgeotrustsslseal
45 ms
symbol_EUR.png
1487 ms
currencylayer-API
141 ms
symbol_GBP.png
1408 ms
symbol_HUF.png
1408 ms
symbol_IDR.png
1454 ms
symbol_ILS.png
1453 ms
analytics.js
140 ms
cb=gapi.loaded_0
32 ms
cb=gapi.loaded_1
61 ms
sharebutton
130 ms
symbol_INR.png
1425 ms
postmessageRelay
120 ms
collect
70 ms
rs=AGLTcCMjQOKLzmHw4jAL4LZH64_0PwYekw
14 ms
rs=AGLTcCPhiVdXuCho9ZcDrO9lL8v41bu2FQ
39 ms
symbol_JPY.png
1369 ms
symbol_KRW.png
1380 ms
symbol_MXN.png
1388 ms
symbol_MYR.png
1419 ms
collect
114 ms
api.js
45 ms
core:rpc:shindig.random:shindig.sha1.js
122 ms
2536007149-postmessagerelay.js
86 ms
symbol_PLN.png
1320 ms
symbol_SEK.png
1414 ms
135 ms
xd_arbiter.php
425 ms
symbol_TRY.png
1362 ms
symbol_VND.png
1373 ms
symbol_ZAR.png
1377 ms
rates_x2.png
1400 ms
integration_x2.png
1343 ms
functionality_x2.png
1417 ms
budget_x2.png
1360 ms
data_x2.png
1374 ms
updates_x2.png
1364 ms
https_x2.png
1392 ms
documentation_x2.png
1349 ms
support_x2.png
1344 ms
usage_x2.png
1351 ms
global_x2.png
1374 ms
historical_x2.png
1366 ms
optional_x2.png
1385 ms
single_conversion_x2.png
1359 ms
timeframe_x2.png
1346 ms
change_x2.png
1349 ms
more_x2.png
1370 ms
currencylayer_promo_bg.png
1370 ms
currencylayer.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
currencylayer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
currencylayer.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Currencylayer.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 Currencylayer.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.
currencylayer.com
Open Graph description is not detected on the main page of Currency Layer. 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: