6.2 sec in total
1.1 sec
4.3 sec
871 ms
Welcome to randor.com homepage info - get ready to check Randor best content right away, or after learning these important things about randor.com
Randor Jewellery Store is located in downtown Toronto specializing in GIA certified loose Diamonds & custom designed engagement rings.
Visit randor.comWe analyzed Randor.com page load time and found that the first response time was 1.1 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
randor.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value6.5 s
9/100
25%
Value10.0 s
9/100
10%
Value410 ms
67/100
30%
Value0.175
69/100
15%
Value12.6 s
14/100
10%
1099 ms
68 ms
81 ms
83 ms
78 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Randor.com, 20% (20 requests) were made to and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cloud.typography.com.
Page size can be reduced by 1.1 MB (47%)
2.4 MB
1.3 MB
In fact, the total size of Randor.com main page is 2.4 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 62.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. 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 62.7 kB or 80% of the original size.
Potential reduce by 42.5 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. Randor images are well optimized though.
Potential reduce by 611.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 611.3 kB or 73% of the original size.
Potential reduce by 422.9 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. Randor.com needs all CSS files to be minified and compressed as it can save up to 422.9 kB or 86% of the original size.
Number of requests can be reduced by 48 (60%)
80
32
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Randor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
randor.com
1099 ms
wp-emoji-release.min.js
68 ms
styles.css
81 ms
basic.css
83 ms
blackwhite.css
78 ms
rgs.css
76 ms
font-awesome.min.css
61 ms
steadysets.css
79 ms
linecon.css
82 ms
style.css
90 ms
responsive.css
109 ms
orbit.css
83 ms
jquery.js
105 ms
jquery-migrate.min.js
90 ms
smp-modal-min.js
91 ms
responsive.js
91 ms
modernizr.js
93 ms
jquery.easing.min.js
106 ms
fonts.css
1520 ms
core.min.js
96 ms
widget.min.js
96 ms
position.min.js
97 ms
menu.min.js
97 ms
autocomplete.min.js
98 ms
wpss-search-suggest.js
102 ms
hoverIntent.min.js
101 ms
ubermenu.min.js
100 ms
jquery.form.min.js
100 ms
scripts.js
98 ms
superfish.js
98 ms
easing.js
100 ms
respond.js
102 ms
swipe.min.js
102 ms
nicescroll.js
102 ms
sticky.js
102 ms
prettyPhoto.js
103 ms
jquery.flexslider-min.js
103 ms
jquery.isotope.min.js
104 ms
imagesLoaded.min.js
100 ms
carouFredSel.min.js
88 ms
appear.js
81 ms
init.js
76 ms
orbit.js
67 ms
blog-masonry.js
67 ms
comment-reply.min.js
64 ms
nectar-love.js
61 ms
wp-embed.min.js
60 ms
style.css
58 ms
responsive.css
69 ms
4362.js
61 ms
analytics.js
159 ms
randor.com
1093 ms
transparent.png
70 ms
logo.png
187 ms
SMALL-Diamond_Price_Guarantee.png
70 ms
badge.png
411 ms
nav-inspiration.jpg
70 ms
btn-customCAM21.jpg
188 ms
img-mens-wedding-rings-thumb1.jpg
187 ms
img-Womens-wedding-rings-thumb.jpg
1061 ms
nav-meethosts.jpg
190 ms
img-4Cs-thumb.jpg
188 ms
img-diamondshapes-thumb.jpg
189 ms
R9860B-large-150x150.png
352 ms
loading.gif
342 ms
re_bttn.png
346 ms
ico.png
352 ms
img.png
403 ms
banner3.png
406 ms
open-close-ico-1.png
353 ms
2ePznZD8BUiJI5A==
16 ms
guEUr3UDwK9oDTRnY3iJKVBRRMw94JOAOdug7RAU9EWSKw8Q5hi8VsaWqZX2S+pgVjuHTPJ6jqYjMgN+01miHMWzIIPWAU5FPjqRCMA0yyj0IR6TfvtRxViVZGLGd8AJRep4L5zWVJ781WOQcXWmFGcC96+ZdN+d0cyqXfFjuOOfidrrBxe0lZNfXWQhUIX1ZMfHLJPLkqXDuLeMomf1RTKW2ePTDDhn88b2qzRC6WtBihhXsECzuaS3kpedfQUnSZnQ+tFY4LsqBmIvz5Knt9Fzj+bef3vZk+ucUvwDuY0jM
20 ms
vhe1OYE2kryYvoV7BAI97wW9vLzryFnaQs+HxqSrpB5T8xFafzYdnyu8fzbz297PP5zsp9i1Ejo
21 ms
AVIiSOQ=
20 ms
guEUr3UDwK9oDTRnY3iJKVBRRMw94JOAOdug7RAU9EWSKw8Q5hi8VsaWqZX2S+pgVjuHTPJ6jqYjMgN+01miHMWzIIPWAU5FPjqRCMA0yyj0IR6TfvtRxViVZGLGd8AJRep4L5zWVJ781WOQcXWmFGcC96+ZdN+d0cyqXfFjuOOfidrrBxe0lZNfXWQhUIX1ZMfHLJPLkqXDuLeMomf1RTKW2ePTDDhn88b2qzRC6WtBihhXsECzuaS3kpedfQUnSZnQ+tFY4LsqBmIvz5Knt9Fzj+bef3vZk+ucUvwDuY0jM
20 ms
vhe1OYE2kryYvoV7BAI97wW9vLzryFnaQs+HxqSrpB5T8xFafzYdnyu8fzbz297PP5zsp9i1Ejo
19 ms
Am90Rqg=
19 ms
zT8SzUMP0BPyxvqjKGXS15JEMzd8jWDzwQNjLi19DwaIWfN63VrpSFgMlF2XxY8FpUeP5rc9bPZ7+NvlPgA5GrA==
33 ms
pGrA==
32 ms
Odkv3cVIyA==
32 ms
AUjQ
33 ms
dxUjI
33 ms
8BSNA=
32 ms
pGrA==
32 ms
mtz1s9nv42+U+ADkas
32 ms
7J8CzUMD0Bf6wvqjKErpY8kqH5ewTCAw+Evbz4NRQsasHnfUvSlbIYKLk4Sx4LTosaz2993urJ9LfJfwJvdEao
31 ms
flogo.png
315 ms
collect
139 ms
collect
846 ms
ApCARrA=
5 ms
hNe7kak
13 ms
7J8CzUMD0Bf6wvqjKErpY8kqH5ewTCAw+Evbz4NRQsasHnfUvSlbIYKLk4Sx4LTosaz2993urJ9LfJfwKQgEaw
12 ms
3rZWulMVAycVZ8lhwWtR4fuvzVk+mv03+E17uRqQ=
12 ms
fontawesome-webfont.svg
843 ms
collect
64 ms
ajax-loader.gif
114 ms
banner-final.jpg
314 ms
fontawesome-webfont.woff
395 ms
R9860B-large.png
53 ms
R9927-large.png
34 ms
R10138.png
33 ms
randor.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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
randor.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
randor.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Randor.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 Randor.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.
randor.com
Open Graph data is detected on the main page of Randor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: