1.7 sec in total
76 ms
1.4 sec
208 ms
Visit ounce.me now to see the best up-to-date Ounce content for Canada and also check out these interesting facts you probably never knew about ounce.me
Ounce.me converts, compares, and charts Bitcoin and Litecoin to Precious Metals. Now with real-time price alerts! What's an ounce today? Get notified when markets move.
Visit ounce.meWe analyzed Ounce.me page load time and found that the first response time was 76 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ounce.me performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.6 s
35/100
25%
Value3.0 s
94/100
10%
Value250 ms
85/100
30%
Value0.001
100/100
15%
Value6.2 s
63/100
10%
76 ms
193 ms
84 ms
148 ms
140 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 61% of them (42 requests) were addressed to the original Ounce.me, 9% (6 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (845 ms) belongs to the original domain Ounce.me.
Page size can be reduced by 352.4 kB (40%)
888.7 kB
536.3 kB
In fact, the total size of Ounce.me main page is 888.7 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. 55% of websites need less resources to load. Images take 389.3 kB which makes up the majority of the site volume.
Potential reduce by 35.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 35.3 kB or 79% of the original size.
Potential reduce by 105.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, Ounce needs image optimization as it can save up to 105.7 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 79.6 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 79.6 kB or 26% of the original size.
Potential reduce by 131.8 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. Ounce.me needs all CSS files to be minified and compressed as it can save up to 131.8 kB or 86% of the original size.
Number of requests can be reduced by 20 (31%)
65
45
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ounce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ounce.me
76 ms
ounce.me
193 ms
jquery.min.js
84 ms
bootstrap2.js
148 ms
full.css
140 ms
bootstrap2.css
178 ms
css
115 ms
css
125 ms
adsbygoogle.js
97 ms
app.js
157 ms
jsapi
98 ms
classic-081711.css
97 ms
email_address.png
148 ms
twitter-icon.png
149 ms
facebook-icon.png
150 ms
android_application.png
149 ms
ounceme_android_app.png
220 ms
ca-pub-0641766429249335.js
21 ms
zrt_lookup.html
37 ms
show_ads_impl.js
57 ms
23 ms
bg-shader2.png
167 ms
navigate-bitcoin-markets-tile2.png
252 ms
top-nav-bg2.png
252 ms
bitcoins-per-troy-ounce-of-gold.png
285 ms
bitcoins-per-troy-ounce-of-silver.png
284 ms
ounce-me-logo.png
320 ms
dismiss-chart.png
287 ms
trending-bitcoin-news2.png
360 ms
chart-middle2.jpg
367 ms
best-place-to-buy-and-sell-bitcoins.png
428 ms
create-alert-bell-small.png
400 ms
bitcoinblocksmall.png
417 ms
dollar-sign-small.png
452 ms
filmstrip-small-transparent.png
663 ms
periodsmall.png
479 ms
bitcoin-litecoin-gold-silver-price-charts.png
611 ms
delta-buttons.png
611 ms
litecoinblocksmall.png
662 ms
goldblocksmall.png
689 ms
silverblocksmall.png
691 ms
platinumblocksmall.png
725 ms
palladiumblocksmall.png
726 ms
oilblocksmall.png
747 ms
sp500index.png
747 ms
10yrblocksmall.png
782 ms
yield-sign-small.png
800 ms
usdollarindexblocksmall.png
831 ms
ethereumblocksmall.png
835 ms
ounceme-donate.png
845 ms
ui+en.css
7 ms
format+en,default+en,ui+en,annotatedtimeline+en.I.js
72 ms
APH4jr0uSos5wiut5cpjronF5uFdDttMLvmWuJdhhgs.ttf
119 ms
glyphicons-halflings-regular.woff
837 ms
ads
244 ms
annotatedtimeline.css
7 ms
osd.js
30 ms
analytics.js
56 ms
feed.txt
708 ms
collect
19 ms
287 ms
clk
66 ms
ca
73 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
42 ms
lidar.js
10 ms
nwf17037_MutualFunds_OutofJuice_728x90_40k.swf.html
20 ms
runtime.js
41 ms
m
26 ms
activeview
15 ms
ounce.me accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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.
ounce.me 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
General
Impact
Issue
Detected JavaScript libraries
ounce.me 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ounce.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ounce.me 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.
ounce.me
Open Graph data is detected on the main page of Ounce. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: