2.5 sec in total
78 ms
1.6 sec
801 ms
Click here to check amazing Rendia content for United States. Otherwise, check out these important facts you probably never knew about rendia.com
Partner with Rendia to create meaningful connections with your patients and grow your eye care or ENT practice.
Visit rendia.comWe analyzed Rendia.com page load time and found that the first response time was 78 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
rendia.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value13.6 s
0/100
25%
Value9.6 s
11/100
10%
Value830 ms
35/100
30%
Value0.122
84/100
15%
Value15.2 s
7/100
10%
78 ms
22 ms
69 ms
44 ms
36 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 71% of them (85 requests) were addressed to the original Rendia.com, 11% (13 requests) were made to Cdn.statically.io and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (788 ms) relates to the external source Cdn.statically.io.
Page size can be reduced by 216.2 kB (12%)
1.8 MB
1.6 MB
In fact, the total size of Rendia.com main page is 1.8 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. 80% 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.2 MB which makes up the majority of the site volume.
Potential reduce by 170.4 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 170.4 kB or 82% of the original size.
Potential reduce by 180 B
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. Rendia images are well optimized though.
Potential reduce by 18.4 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 18.4 kB or 11% of the original size.
Potential reduce by 27.2 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. Rendia.com needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 11% of the original size.
Number of requests can be reduced by 76 (75%)
102
26
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rendia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
rendia.com
78 ms
icons.min.css
22 ms
style.css
69 ms
frontend.min.css
44 ms
flatpickr.min.css
36 ms
select2.min.css
37 ms
style.css
82 ms
front.min.css
52 ms
style.min.css
73 ms
style.min.css
54 ms
front.min.css
78 ms
all.css
162 ms
magnific_popup.css
88 ms
formreset.min.css
78 ms
formsmain.min.css
96 ms
readyclass.min.css
89 ms
browsers.min.css
91 ms
dashicons.min.css
102 ms
style.dev.css
173 ms
style.css
108 ms
v4-shims.css
223 ms
jquery.min.js
104 ms
jquery-migrate.min.js
106 ms
icons.min.js
137 ms
flatpickr.min.js
115 ms
select2.min.js
124 ms
ie-compat.min.js
135 ms
jquery.bind-first-0.2.3.min.js
129 ms
js.cookie-2.1.3.min.js
164 ms
public.js
141 ms
jquery.json.min.js
142 ms
gravityforms.min.js
162 ms
placeholders.jquery.min.js
170 ms
dc7555e25a.js
67 ms
css
43 ms
mediaelementplayer-legacy.min.css
160 ms
wp-mediaelement.min.css
160 ms
tooltipster.bundle.min.css
215 ms
frontend-builder-global-functions.js
302 ms
frontend.min.js
216 ms
idle-timer.min.js
215 ms
custom.js
360 ms
front.min.js
275 ms
jquery.mobile.custom.min.js
273 ms
custom.js
177 ms
frontend-builder-scripts.js
257 ms
frontend-bundle.min.js
291 ms
frontend-bundle.min.js
287 ms
front.min.js
281 ms
jquery.fitvids.js
278 ms
waypoints.min.js
273 ms
jquery.magnific-popup.js
271 ms
common.js
269 ms
mediaelement-and-player.min.js
270 ms
mediaelement-migrate.min.js
269 ms
wp-mediaelement.min.js
262 ms
vimeo.min.js
258 ms
tooltipster.bundle.min.js
258 ms
jquery.easypiechart.js
258 ms
et_shortcodes_frontend.js
255 ms
gtm.js
477 ms
Eye_Anter_Angle_revised.jpg
452 ms
ENT_L-Lat_revised.jpg
453 ms
Eye_L-Lat_Scatter_revised.jpg
453 ms
CareJourney.png
454 ms
icon-plus.png
454 ms
CareJourney_Step1.png
553 ms
flow-arrow.png
553 ms
CareJourney_Step3.png
564 ms
CareJourney_Step4.png
556 ms
concept-of-contact-lenses-for-eyes-health-care-2021-09-04-01-27-11-utc-min-1350x900.jpg
653 ms
Facebook.png
781 ms
LinkedIn.png
788 ms
green-dot.png
284 ms
lottie_homepage.gif
452 ms
HVD-Fonts-BrandonText-Regular.otf
222 ms
HVD-Fonts-BrandonText-Bold-1.otf
386 ms
modules.ttf
388 ms
inspectlet.js
527 ms
White.png
181 ms
hero.png
447 ms
dry_eye_hero.jpg
214 ms
Eye_Anter_Angle_revised.jpg
140 ms
ENT_L-Lat_revised.jpg
140 ms
Eye_L-Lat_Scatter_revised.jpg
209 ms
icon-plus.png
133 ms
CareJourney.png
137 ms
js
71 ms
optimize.js
160 ms
conversion_async.js
159 ms
uwt.js
153 ms
insight.min.js
242 ms
CareJourney_Step1.png
107 ms
flow-arrow.png
106 ms
CareJourney_Step4.png
105 ms
CareJourney_Step2.png
103 ms
CareJourney_Step5.png
132 ms
CareJourney_Step3.png
227 ms
boy-playing-pickleball-2022-08-01-01-15-12-utc-min-1350x900.jpg
214 ms
granddaughter-embracing-her-grandmother-2022-03-08-01-32-55-utc-min-1350x900.jpg
213 ms
Blue.png
146 ms
concept-of-contact-lenses-for-eyes-health-care-2021-09-04-01-27-11-utc-min-1350x900.jpg
154 ms
app_store-2.png
136 ms
227146806
171 ms
analytics.js
73 ms
121 ms
Twitter.png
82 ms
Facebook.png
60 ms
LinkedIn.png
54 ms
YouTube.png
65 ms
adsct
139 ms
adsct
158 ms
Ellipse-14.png
51 ms
collect
54 ms
hero.png
55 ms
collect
21 ms
19 ms
ga-audiences
25 ms
16 ms
rendia.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
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.
rendia.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
rendia.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Rendia.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 Rendia.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.
rendia.com
Open Graph data is detected on the main page of Rendia. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: