Casara.In - Info receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in India and links to network IP address This server doesn't support HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

Web Servers
Font Scripts
Font Awesome
OWL Carousel
Programming Languages
Operating Systems
JavaScript Libraries
jQuery Profile

Title: CA Sangeetha & Ramya | Home
Last update was 123 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Ovi Hosting Pvt Ltd 
Server Location:

India, IN

Other sites hosted on

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First Contentful Paint 3.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 50 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 4.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Contentful Paint (3G) 5982 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 2,503 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

616 KB
579 KB
537 KB
276 KB
78 KB
63 KB
62 KB
45 KB
40 KB
33 KB
Minimizes main-thread work - 0.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Time Spent
255 ms
Script Evaluation
202 ms
Style & Layout
181 ms
114 ms
Parse HTML & CSS
85 ms
Script Parsing & Compilation
36 ms
Serve images in next-gen formats - Potential savings of 2,002 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
615 KB586 KB
579 KB563 KB
536 KB526 KB
276 KB236 KB
45 KB30 KB
61 KB19 KB
29 KB18 KB
26 KB15 KB
39 KB9 KB
Avoids an excessive DOM size - 358 elements
A large DOM will increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Minify JavaScript - Potential savings of 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

SizePotential Savings
9 KB4 KB
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 43 requests • 2,503 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
432503 KB
192311 KB
386 KB
863 KB
1136 KB
16 KB
10 KB
00 KB
324 KB
Eliminate render-blocking resources - Potential savings of 1,050 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
6 KB480
17 KB930
33 KB1230
1 KB330
1 KB330
9 KB780
4 KB330
1 KB180
Efficiently encode images - Potential savings of 1,307 KB
Optimized images load faster and consume less cellular data. Learn more.

SizePotential Savings
615 KB563 KB
579 KB547 KB
276 KB185 KB
45 KB12 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms301 ms0 KB0 KB301text/html
301 ms859 ms6 KB30 KB200text/htmlDocument
871 ms1146 ms6 KB26 KB200text/cssStylesheet
872 ms1433 ms17 KB96 KB200text/cssStylesheet
872 ms1425 ms33 KB94 KB200application/javascriptScript
872 ms1148 ms1 KB1 KB200text/cssStylesheet
873 ms1147 ms1 KB2 KB200text/cssStylesheet
873 ms1150 ms9 KB52 KB200application/javascriptScript
873 ms1147 ms4 KB16 KB200text/cssStylesheet
873 ms1150 ms1 KB1 KB200text/cssStylesheet
874 ms1422 ms27 KB26 KB200image/pngImage
874 ms1418 ms29 KB29 KB200image/pngImage
1459 ms2274 ms78 KB78 KB200image/jpegImage
1459 ms2014 ms62 KB61 KB200image/jpegImage
1459 ms2811 ms276 KB276 KB200image/jpegImage
1459 ms2297 ms40 KB39 KB200image/jpegImage
1459 ms1736 ms1 KB0 KB200image/pngImage
1459 ms1739 ms1 KB1 KB200image/pngImage
1459 ms1736 ms1 KB1 KB200image/pngImage
1460 ms1738 ms1 KB1 KB200image/pngImage
1460 ms3099 ms616 KB615 KB200image/jpegImage
1460 ms3110 ms579 KB579 KB200image/jpegImage
1460 ms2279 ms45 KB45 KB200image/jpegImage
1460 ms2001 ms15 KB14 KB200image/pngImage
1460 ms3123 ms537 KB536 KB200image/pngImage
1419 ms1696 ms2 KB8 KB200text/cssStylesheet
1423 ms1697 ms1 KB3 KB200text/cssStylesheet
1457 ms1734 ms9 KB28 KB200application/javascriptScript
1458 ms1737 ms1 KB2 KB200application/javascriptScript
1458 ms1735 ms2 KB3 KB200application/javascriptScript
1458 ms1737 ms1 KB0 KB200application/javascriptScript
1458 ms1748 ms1 KB0 KB200text/cssStylesheet
1460 ms1736 ms0 KB0 KB200image/gifImage
1461 ms1791 ms1 KB1 KB200image/pngImage
1458 ms1737 ms1 KB1 KB200text/cssStylesheet
1458 ms2013 ms1 KB1 KB200application/javascriptScript
1459 ms1739 ms8 KB28 KB200application/javascriptScript
1461 ms1738 ms2 KB1 KB200image/gifImage,700
1457 ms1476 ms1 KB5 KB200text/cssStylesheet
1483 ms2025 ms1 KB1 KB200image/pngImage
1486 ms1490 ms11 KB11 KB200font/woff2Font
1487 ms2568 ms63 KB63 KB200application/octet-streamFont
1488 ms1491 ms11 KB11 KB200font/woff2Font
Serve static assets with an efficient cache policy - 38 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms63 KB
1209428000 ms33 KB
1209428000 ms29 KB
1209428000 ms27 KB
1209428000 ms17 KB
1209428000 ms9 KB
1209428000 ms6 KB
1209428000 ms4 KB
1209428000 ms1 KB
1209428000 ms1 KB
1209428000 ms1 KB
1209429000 ms616 KB
1209429000 ms579 KB
1209429000 ms537 KB
1209429000 ms276 KB
1209429000 ms78 KB
1209429000 ms62 KB
1209429000 ms45 KB
1209429000 ms40 KB
1209429000 ms15 KB
1209429000 ms9 KB
1209429000 ms8 KB
1209429000 ms2 KB
1209429000 ms2 KB
1209429000 ms2 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms1 KB
1209429000 ms0 KB
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
878 ms
7 ms
888 ms
7 ms
1455 ms
22 ms
1495 ms
23 ms
1521 ms
7 ms
1769 ms
7 ms
2031 ms
33 ms
2300 ms
10 ms
2585 ms
6 ms
2600 ms
9 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
3 ms
1082 ms
3 ms
JavaScript execution time - 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
637 ms12 ms4 ms
103 ms97 ms1 ms
91 ms75 ms7 ms
Defer offscreen images - Potential savings of 29 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
29 KB29 KB
Properly size images - Potential savings of 37 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

SizePotential Savings
78 KB37 KB
Remove unused CSS - Potential savings of 16 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
17 KB16 KB
Avoid chaining critical requests - 22 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 560 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1.8MiB (83% reduction).

Compressing could save 577.9KiB (93% reduction).
Compressing could save 555.9KiB (96% reduction).
Compressing could save 475.3KiB (88% reduction).
Compressing could save 211.4KiB (76% reduction).
Compressing could save 22KiB (50% reduction).
Compressing could save 18.7KiB (65% reduction).
Compressing could save 14.5KiB (24% reduction).
Compressing could save 11.9KiB (16% reduction).
Compressing could save 5.5KiB (15% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 7 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:***8597,700

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 1.8KiB (21% reduction).

Minifying could save 1.8KiB (21% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 756B (13% reduction).

Minifying could save 756B (13% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 310B (28% reduction).

Minifying could save 196B (32% reduction) after compression.
Minifying could save 114B (22% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="#componentlayout308223"></a> is close to 1 other tap targets .
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 30.12 KB
Compressed size: 6.04 KB
File reduced by: 24.08 KB (79%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify does not support HTTPS
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Fri, 31 Jan 2020 13:38:19 GMT
Server: Apache/2.4.7 (Ubuntu)
Content-Length: 303
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Date: Fri, 31 Jan 2020 13:38:20 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/
Set-Cookie: symfony=1k131sn9j1g6u02d0313f4uoq1; path=/
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 6188
Content-Type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
MX 600
MX 600
SOA 600
Serial Number 2018052301
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 0
A 600
NS 2578
NS 2578

+ Whois Lookup

Domain Created:
Domain Age:

Currently Not Available
Last update was 123 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget