1.3 sec in total
77 ms
876 ms
311 ms
Visit data64.in now to see the best up-to-date Data 64 content for India and also check out these interesting facts you probably never knew about data64.in
Discover the most powerful framework for data analytics and business intelligence.
Visit data64.inWe analyzed Data64.in page load time and found that the first response time was 77 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
data64.in performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value14.4 s
0/100
25%
Value9.1 s
14/100
10%
Value880 ms
32/100
30%
Value0.086
93/100
15%
Value14.4 s
9/100
10%
77 ms
94 ms
53 ms
32 ms
5 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 50% of them (70 requests) were addressed to the original Data64.in, 35% (49 requests) were made to Maps.googleapis.com and 6% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (236 ms) belongs to the original domain Data64.in.
Page size can be reduced by 871.1 kB (20%)
4.3 MB
3.5 MB
In fact, the total size of Data64.in main page is 4.3 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. Only a small number of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 57.6 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. This page needs HTML code to be minified as it can gain 10.3 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.6 kB or 86% of the original size.
Potential reduce by 32.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. Data 64 images are well optimized though.
Potential reduce by 580.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 580.9 kB or 69% of the original size.
Potential reduce by 200.6 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. Data64.in needs all CSS files to be minified and compressed as it can save up to 200.6 kB or 89% of the original size.
Number of requests can be reduced by 65 (50%)
131
66
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data 64. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
data64.in
77 ms
www.data64.in
94 ms
style.css
53 ms
jquery.js
32 ms
plugins.js
5 ms
jquery.form.js
22 ms
main.js
38 ms
css
25 ms
fonts.css
7 ms
jquery.mCustomScrollbar.css
4 ms
jquery.mCustomScrollbar.min.js
8 ms
animate.css
10 ms
delays.css
7 ms
flexslider.css
9 ms
animation_delays.css
11 ms
jquery.flexslider-min.js
13 ms
mediaelementplayer.css
12 ms
mediaelement-and-player.min.js
17 ms
jquery.sort.min.js
15 ms
jquery.scroll.to.min.js
15 ms
prettyPhoto.css
15 ms
jquery.prettyPhoto.js
27 ms
jquery.tools.min.js
26 ms
jquery.queryloader2.min.js
29 ms
js
30 ms
logo_top.png
22 ms
counter.js
13 ms
loader_1.gif
12 ms
arrow_1.png
10 ms
pic_parallax_1.jpg
135 ms
bg_caption_1.png
10 ms
bg_projects_1.jpg
10 ms
investigation.jpg
123 ms
investigation_big.jpg
122 ms
work.jpg
120 ms
work_big.jpg
119 ms
dc5.jpg
124 ms
dc5_big.jpg
125 ms
crypto.jpg
123 ms
crypto_big.jpg
126 ms
internet2.jpg
124 ms
internet2_big.jpg
131 ms
hire.jpg
126 ms
hire_big.jpg
141 ms
industrial.jpg
138 ms
industrial_big.jpg
127 ms
knowledge.jpg
136 ms
knowledge_big.jpg
130 ms
pic_parallax_2.jpg
141 ms
bg_window_1.jpg
131 ms
pic_project_undone.jpg
133 ms
pic_project_done.jpg
134 ms
bg_scroll_dragger_2.png
132 ms
curve_1.png
133 ms
curve_2.png
133 ms
curve_3.png
137 ms
curve_4.png
134 ms
curve_5.png
135 ms
curve_6.png
138 ms
pic_parallax_3.jpg
236 ms
bg_contacts.png
135 ms
button_up_1.png
135 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
112 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
112 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
112 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
111 ms
t.php
116 ms
common.js
74 ms
map.js
76 ms
util.js
76 ms
geocoder.js
74 ms
icon_menu_1.gif
31 ms
arrow_2.png
124 ms
bg_stats_2.png
30 ms
sprite_social_1.png
126 ms
marker_1.png
31 ms
sprite_slider_nav_1.png
117 ms
sprite_arrow_6.png
119 ms
icon_zoom_1.png
116 ms
icon_lnk_1.png
115 ms
sprite_arrow_1.gif
115 ms
onion.js
31 ms
openhand_8_8.cur
23 ms
AuthenticationService.Authenticate
130 ms
GeocodeService.Search
40 ms
ViewportInfoService.GetViewportInfo
75 ms
stats.js
28 ms
controls.js
17 ms
transparent.png
21 ms
css
55 ms
google4.png
40 ms
marker.js
33 ms
mapcnt6.png
48 ms
sv5.png
54 ms
tmapctrl.png
24 ms
cb_scout5.png
26 ms
tmapctrl4.png
25 ms
imgs8.png
25 ms
vt
35 ms
vt
27 ms
vt
25 ms
vt
25 ms
vt
26 ms
vt
27 ms
vt
26 ms
vt
53 ms
vt
27 ms
vt
54 ms
vt
27 ms
vt
57 ms
vt
55 ms
vt
55 ms
vt
27 ms
vt
57 ms
vt
54 ms
vt
58 ms
vt
56 ms
vt
57 ms
vt
58 ms
vt
59 ms
vt
60 ms
vt
64 ms
vt
58 ms
vt
65 ms
vt
66 ms
vt
67 ms
vt
85 ms
vt
82 ms
vt
71 ms
vt
72 ms
vt
67 ms
vt
86 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
13 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
14 ms
vt
61 ms
vt
54 ms
ViewportInfoService.GetViewportInfo
81 ms
marker_map_1_act.png
9 ms
infowindow.js
11 ms
data64.in 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
data64.in 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
data64.in 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
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Data64.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Data64.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.
data64.in
Open Graph description is not detected on the main page of Data 64. 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: