3.8 sec in total
67 ms
3 sec
789 ms
Welcome to recly.com homepage info - get ready to check Recly best content right away, or after learning these important things about recly.com
Visit recly.comWe analyzed Recly.com page load time and found that the first response time was 67 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
recly.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value78.5 s
0/100
25%
Value25.3 s
0/100
10%
Value1,510 ms
14/100
30%
Value0.009
100/100
15%
Value44.8 s
0/100
10%
67 ms
2150 ms
106 ms
54 ms
48 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that all of those requests were addressed to Recly.com and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Recly.com.
Page size can be reduced by 2.1 MB (14%)
14.9 MB
12.9 MB
In fact, the total size of Recly.com main page is 14.9 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. 50% of websites need less resources to load. Images take 14.9 MB which makes up the majority of the site volume.
Potential reduce by 38.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 38.9 kB or 78% of the original size.
Potential reduce by 2.0 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, Recly needs image optimization as it can save up to 2.0 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Number of requests can be reduced by 9 (35%)
26
17
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
recly.com
67 ms
recly.com
2150 ms
9104f4c0f18b79d1.css
106 ms
polyfills-c67a75d1b6f99dc8.js
54 ms
webpack-94547de1949c56d7.js
48 ms
framework-2c79e2a64abdb08b.js
44 ms
main-2a00b172203e08ea.js
154 ms
_app-5be35f2a5ad6aa42.js
172 ms
15-1f92b5867b0c1370.js
170 ms
480-fe16f1a75c78b89d.js
134 ms
index-e00963bb4527a375.js
144 ms
_buildManifest.js
202 ms
_ssgManifest.js
136 ms
solid-logo.svg
294 ms
image
144 ms
image
146 ms
image
148 ms
image
149 ms
image
150 ms
image
178 ms
image
152 ms
image
154 ms
image
156 ms
image
158 ms
image
159 ms
image
161 ms
image
163 ms
home-hero.png
619 ms
Regular.e31b1640.ttf
87 ms
Medium.d085e2bf.ttf
151 ms
Light.147134ae.ttf
92 ms
ExtraLight.5feffe0d.ttf
119 ms
Thin.8d966e43.ttf
195 ms
SemiBold.dcee20d5.ttf
125 ms
Bold.ff724a77.ttf
151 ms
ExtraBold.7a9bebb4.ttf
236 ms
Black.f8087ce9.ttf
227 ms
%2Fimages%2Fhome_section_1-1.jpg
203 ms
%2Fimages%2Fhome_section_1-2.jpg
211 ms
%2Fimages%2Fhome_section_1-3.jpg
298 ms
%2Fimages%2Fhome_section_2-1.png
245 ms
%2Fimages%2Fhome_section_2-2.png
282 ms
%2Fimages%2Fhome_section_3-2.png
242 ms
%2Fimages%2Fhome_section_4-1.png
255 ms
%2Fimages%2Fhome_section_4-2.png
293 ms
%2Fimages%2Fhome_section_4-3.png
306 ms
%2Fimages%2Fhome_section_4-4.png
311 ms
%2Fimages%2Fdownload_appstore-dark.png
329 ms
%2Fimages%2Fdownload_gplay-dark.png
332 ms
%2Fimages%2Fhome_section_3-1.png
378 ms
ExtraLight.fb3c4772.woff2
314 ms
Thin.6dbb8d02.woff2
329 ms
Light.aabd7d47.woff2
352 ms
Regular.c935de02.woff2
320 ms
Medium.92a1579f.woff2
379 ms
SemiBold.5967db3f.woff2
397 ms
Bold.70636a1c.woff2
435 ms
ExtraBold.0b809223.woff2
413 ms
Black.849d2e9b.woff2
437 ms
recly.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
recly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
recly.com SEO score
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recly.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Recly.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.
recly.com
Open Graph description is not detected on the main page of Recly. 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: