6.7 sec in total
398 ms
4.7 sec
1.6 sec
Click here to check amazing Equentis content. Otherwise, check out these important facts you probably never knew about equentis.com
Discover top-notch investment advisory services with expert investment advisor to help you achieve your financial goals. Start your journey today!
Visit equentis.comWe analyzed Equentis.com page load time and found that the first response time was 398 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
equentis.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value10.3 s
0/100
25%
Value16.2 s
0/100
10%
Value2,470 ms
4/100
30%
Value0.003
100/100
15%
Value32.3 s
0/100
10%
398 ms
956 ms
28 ms
29 ms
187 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 54% of them (61 requests) were addressed to the original Equentis.com, 28% (32 requests) were made to Equentis-web.s3.ap-south-1.amazonaws.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Equentis-web.s3.ap-south-1.amazonaws.com.
Page size can be reduced by 934.9 kB (9%)
10.5 MB
9.5 MB
In fact, the total size of Equentis.com main page is 10.5 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. 65% of websites need less resources to load. Images take 10.1 MB which makes up the majority of the site volume.
Potential reduce by 175.1 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 175.1 kB or 87% of the original size.
Potential reduce by 755.8 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. Equentis images are well optimized though.
Potential reduce by 3.9 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 50 (48%)
104
54
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Equentis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
equentis.com
398 ms
www.equentis.com
956 ms
moe_webSdk_webp.min.latest.js
28 ms
moe_webSdk.min.latest.js
29 ms
serviceworker.js
187 ms
astrra.sdk.js
454 ms
Tracker.js
47 ms
52afe5bf2fc862f4.css
563 ms
aa15fe3776697b1b.css
747 ms
73c00cd95dc66651.css
578 ms
4df78f2cd73d6b26.css
561 ms
polyfills-c67a75d1b6f99dc8.js
851 ms
snippet.js
52 ms
webpack-bf0911911cd1a5bb.js
578 ms
framework-314c182fa7e2bf37.js
869 ms
main-f446f655120d60d4.js
961 ms
_app-c9ab8e51b4f4cad2.js
962 ms
1876-1af9b0dd0ec7e978.js
876 ms
6066-c4c03e4a9803593d.js
962 ms
8159-1a2b2dc87a999b1b.js
964 ms
5121-63b8f56638617878.js
964 ms
7555-6562d13ea93eff71.js
968 ms
2078-d11575ef7f6cf846.js
1135 ms
9238-8af1829ef0aa0058.js
1132 ms
5136-0a1ee24646e22d20.js
1135 ms
2074-2549dfc0166b4250.js
1133 ms
4023-ad3e7278adcf702b.js
1133 ms
5801-87ded713d92b86f0.js
1146 ms
index-2aa9ab2447829ff5.js
1322 ms
_buildManifest.js
1319 ms
_ssgManifest.js
1324 ms
ej9grpps4q
82 ms
fbevents.js
24 ms
obtp.js
54 ms
bat.js
49 ms
1705907482287-Logo.png
896 ms
equentis_logo.svg
1132 ms
whoicon.png
1128 ms
videoicon.png
1144 ms
mediaicon.png
1312 ms
contacticon.png
1314 ms
bull-icon-logo.svg
1314 ms
user_icon.png
1316 ms
user_icon_1.png
1316 ms
ai_icon.png
1333 ms
Offerings_RNR.png
1869 ms
Offerings_EPW.png
1684 ms
Offerings_IIR.png
1872 ms
1705907582105-Logo%20%281%29.png
891 ms
trade_Mark_ec12bd4b2c.png
1076 ms
icon_personalised_portfolio_0c28c6fc13.png
893 ms
Group_9_857948b7bc.png
892 ms
icon_ai_algorithm_efe258f10d.png
890 ms
ic_deployingsurplus_1_a55cd501f9.png
1091 ms
Group_1000006125_78345bb5b0.png
1098 ms
Group_1000006124_1a0a7dad3e.png
1169 ms
Group_1000006126_3940afd7ac.png
1099 ms
Group_1000006136_29c3873d5e.png
1093 ms
Group_1000006127_daa3dca4b8.png
1297 ms
Group_1000006128_a10e1fbc76.png
1310 ms
icon_ideal_buying_range_195c8d1c34.png
1317 ms
Group_1000003727_14604edb06.png
1300 ms
Group_1000006640_e6f5f0665a.png
1315 ms
Group_1000005931_7b3ab7f278.png
1417 ms
award_8ba1645928.png
1730 ms
DMA_SPARKIES_78e9886fe5.jfif
2124 ms
RTS_00667_75f99b8ac8.JPG
3080 ms
Offerings_MultiplyRR.png
2055 ms
187104017.js
10 ms
187104017
27 ms
clarity.js
20 ms
Manish-Goel.png
1870 ms
layers.png
1144 ms
image
1625 ms
image
1641 ms
Manish_Goel_3_1fbf1d00da.png
1132 ms
Manish_Goel_5_d90a18e726.png
1194 ms
Manish_Goel_1_74e93eec03.png
1219 ms
Manish_Goel_b448fe0430.png
1531 ms
Sudeendra_a43b2b05f8_d9d119c1d1.jpeg
1368 ms
3a925fad67bebd767375ecd92b0848e5_9f0e958287.jfif
2007 ms
34339c076e15b156a478a8df620458ba_6bfd047268.jfif
1999 ms
0942a8280fe8df645b39c96a17c21086_f453fba674.jfif
2005 ms
af8b0995e67ab7150b5139bbb28c2436_717280668d.jfif
1792 ms
e8178f98a8bffd32e4fc15a737040da8_a37b6abe20.jfif
1979 ms
Manish_Goel_4_77f903b1fe.png
2020 ms
Manish_Goel_2_cc8ce29f82.png
2181 ms
image
1431 ms
image
1497 ms
image
1641 ms
image
1700 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FO_G.woff
20 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFO_G.woff
64 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFO_G.woff
88 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FO_G.woff
90 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE-_G.woff
88 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE-_G.woff
88 ms
xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E-_G.woff
89 ms
image
1660 ms
image
1702 ms
image
1753 ms
image
1793 ms
image
1879 ms
image
1777 ms
image
1726 ms
image
1736 ms
image
1782 ms
image
1821 ms
image
1847 ms
download_button_playStore.svg
1888 ms
download_button_appStore.svg
1724 ms
hero-section.jpg
1732 ms
c.gif
7 ms
equentis.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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Form elements do not have associated labels
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.
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.
equentis.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
equentis.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Equentis.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 Equentis.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.
equentis.com
Open Graph description is not detected on the main page of Equentis. 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: