4.8 sec in total
471 ms
4.2 sec
118 ms
Welcome to opencase.in homepage info - get ready to check Open Case best content for India right away, or after learning these important things about opencase.in
Build and manage custom stock portfolios (baskets) for Indian markets. Connect Zerodha, Angel One and invest with one click. Open source, self-hostable.
Visit opencase.inWe analyzed Opencase.in page load time and found that the first response time was 471 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
opencase.in performance score
name
value
score
weighting
Value5.6 s
6/100
10%
Value5.6 s
18/100
25%
Value9.7 s
11/100
10%
Value4,790 ms
0/100
30%
Value0.076
95/100
15%
Value17.8 s
4/100
10%
471 ms
1036 ms
206 ms
406 ms
590 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 76% of them (63 requests) were addressed to the original Opencase.in, 13% (11 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Opencase.in.
Page size can be reduced by 363.9 kB (33%)
1.1 MB
743.9 kB
In fact, the total size of Opencase.in main page is 1.1 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. Javascripts take 696.4 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.9 kB or 79% of the original size.
Potential reduce by 33.0 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, Open Case needs image optimization as it can save up to 33.0 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 246.0 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 246.0 kB or 35% of the original size.
Potential reduce by 13.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. Opencase.in has all CSS files already compressed.
Number of requests can be reduced by 53 (78%)
68
15
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Open Case. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
opencase.in
471 ms
opencase.in
1036 ms
elementor.min.css
206 ms
swiper.min.css
406 ms
all.min.css
590 ms
style.min.css
1000 ms
css
39 ms
dynamic-styles.css
595 ms
frontend.min.css
602 ms
e-swiper.min.css
607 ms
post-138.css
605 ms
style.css
784 ms
global.css
790 ms
widget-heading.min.css
803 ms
widget-text-editor.min.css
801 ms
post-133.css
805 ms
bootstrap.css
983 ms
bootstrap-theme.css
994 ms
wpbc-tippy-popover.css
1015 ms
wpbc-tippy-times.css
1016 ms
material-design-icons.css
1208 ms
wpbc_ui_both.css
1176 ms
wpbc_time-selector.css
1182 ms
light__24_8.css
1182 ms
client.css
1199 ms
wpbc_fe__form_fields.css
1202 ms
calendar.css
1371 ms
24_9__light_square_1.css
1378 ms
timeline_v2.1.css
1379 ms
css
37 ms
jquery.min.js
1401 ms
jquery-migrate.min.js
1399 ms
js
74 ms
wpbc_all.js
1818 ms
popper.js
1567 ms
tippy-bundle.umd.js
1773 ms
jquery.datepick.wpbc.9.0.js
1577 ms
client.js
1598 ms
create_booking.js
1603 ms
wpbc_times.js
1763 ms
adsbygoogle.js
53 ms
wpbc_time-selector.js
1772 ms
timeline_v2.js
1604 ms
swiper-bundle.min.js
1410 ms
imagesloaded.min.js
1374 ms
bloghash.min.js
1383 ms
underscore.min.js
1378 ms
wp-util.min.js
1401 ms
vanilla-marquee.min.js
1408 ms
google-charts.js
1245 ms
google-chart-render.js
1373 ms
webpack.runtime.min.js
1373 ms
frontend-modules.min.js
1379 ms
core.min.js
1402 ms
frontend.min.js
1220 ms
24_9__light.css
849 ms
logo.png
226 ms
india_tokiyo_olmpics-150x150.jpg
225 ms
Flipkart_SEO-150x150.jpg
225 ms
sales_forecasting-150x150.png
225 ms
amazon_sagemailer-150x150.png
225 ms
amazon_brand_score-150x150.png
226 ms
amazon_sales_analysis-150x150.png
400 ms
helium_tool-150x150.png
401 ms
webscraper.io_-150x150.png
401 ms
bigbasket_reviews-150x150.png
403 ms
fakepost-150x150.png
402 ms
show_ads_impl.js
81 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
90 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
106 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
127 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
155 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
154 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
155 ms
NGSnv5HMAFg6IuGlBNMjxJEL2VmU3NS7Z2mj0QiaWy5X.ttf
155 ms
fa-regular-400.woff
135 ms
fa-solid-900.woff
168 ms
QdVMSTAyLFyeg_IDWvOJmVES_HTEJm81Rbg.ttf
154 ms
QdVPSTAyLFyeg_IDWvOJmVES_Hw3BX8.ttf
154 ms
QdVMSTAyLFyeg_IDWvOJmVES_HSMIG81Rbg.ttf
166 ms
esDR31xSG-6AGleN2tWklQ.ttf
167 ms
zrt_lookup.html
99 ms
ads
110 ms
opencase.in 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.
opencase.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
opencase.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Opencase.in 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 Opencase.in 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.
opencase.in
Open Graph data is detected on the main page of Open Case. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: