4.7 sec in total
184 ms
4.2 sec
234 ms
Welcome to checktimes.com homepage info - get ready to check Check Times best content for India right away, or after learning these important things about checktimes.com
Current time lookup service for World Wide time and date info, which provides current daylight saving time dates and timezone difference between other cities.
Visit checktimes.comWe analyzed Checktimes.com page load time and found that the first response time was 184 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
checktimes.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.2 s
1/100
25%
Value12.6 s
3/100
10%
Value5,520 ms
0/100
30%
Value0.116
85/100
15%
Value20.5 s
2/100
10%
184 ms
554 ms
41 ms
58 ms
60 ms
Our browser made a total of 130 requests to load all elements on the main page. We found that 18% of them (23 requests) were addressed to the original Checktimes.com, 13% (17 requests) were made to Pagead2.googlesyndication.com and 13% (17 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (796 ms) belongs to the original domain Checktimes.com.
Page size can be reduced by 273.4 kB (17%)
1.6 MB
1.3 MB
In fact, the total size of Checktimes.com main page is 1.6 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. 75% 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 722.5 kB which makes up the majority of the site volume.
Potential reduce by 34.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 34.4 kB or 79% of the original size.
Potential reduce by 5.5 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. Check Times images are well optimized though.
Potential reduce by 63.7 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 63.7 kB or 11% of the original size.
Potential reduce by 169.8 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. Checktimes.com needs all CSS files to be minified and compressed as it can save up to 169.8 kB or 84% of the original size.
Number of requests can be reduced by 60 (59%)
101
41
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Check Times. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
checktimes.com
184 ms
checktimes.com
554 ms
css
41 ms
css
58 ms
css
60 ms
bootstrap.css
643 ms
font-awesome.min.css
436 ms
style.css
380 ms
time.css
385 ms
leaflet.css
390 ms
jquery.js
629 ms
bootstrap.min.js
495 ms
respond.min.js
442 ms
html5shiv.js
454 ms
onetrustConsent.js
673 ms
time.js
500 ms
leaflet.js
796 ms
tzdif.js
554 ms
addthis_widget.js
262 ms
adsbygoogle.js
168 ms
optanon.css
60 ms
EU
33 ms
analytics.js
94 ms
checktimes_logo_trans.png
113 ms
chktimebg.png
113 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
77 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
474 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
482 ms
OpNJno4VhNfK-RgpwWWxli1VXg.ttf
547 ms
BngMUXZGTXPUvIoyV6yN5-fN5qA.ttf
544 ms
show_ads_impl.js
432 ms
3.png
423 ms
fontawesome-webfont.woff
578 ms
collect
444 ms
5.png
235 ms
js
83 ms
zrt_lookup.html
76 ms
ads
435 ms
ads
412 ms
ads
452 ms
gen_204
104 ms
pixel
103 ms
8324732904621422289
76 ms
abg_lite.js
39 ms
omrhp.js
32 ms
Q12zgMmT.js
100 ms
window_focus.js
123 ms
qs_click_protection.js
134 ms
ufs_web_display.js
99 ms
icon.png
18 ms
pixel
97 ms
14024861979698393308
95 ms
gen_204
111 ms
reactive_library.js
265 ms
ca-pub-0148477734632100
328 ms
pixel
246 ms
62bHydCX.html
200 ms
activeview
117 ms
ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js
27 ms
rum
53 ms
bounce
32 ms
pixel
32 ms
pixel
34 ms
rum
51 ms
activeview
73 ms
ads
410 ms
ads
209 ms
4750003962995249291
145 ms
load_preloaded_resource.js
143 ms
abg_lite.js
141 ms
5f7468413707c3abfd197d65a482477f.js
335 ms
fullscreen_api_adapter.js
197 ms
interstitial_ad_frame.js
203 ms
feedback_grey600_24dp.png
347 ms
settings_grey600_24dp.png
329 ms
gen_204
317 ms
pixel
317 ms
17645160646965487492
315 ms
pixel
342 ms
cookie_push_onload.html
218 ms
gen_204
242 ms
activeview
242 ms
css
167 ms
pixel
118 ms
pixel
121 ms
usersync.aspx
241 ms
274 ms
activeview
191 ms
um
214 ms
rum
102 ms
setuid
99 ms
pixel
98 ms
pixel
99 ms
pixel
98 ms
pixel
144 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
77 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
77 ms
um
137 ms
rum
83 ms
ecc
90 ms
44 ms
pixel
43 ms
pixel
23 ms
pixel
26 ms
pixel
25 ms
pixel
25 ms
pixel
23 ms
sd
20 ms
pixel
27 ms
408.png
62 ms
409.png
73 ms
408.png
62 ms
marker-icon.png
64 ms
sodar
99 ms
409.png
62 ms
408.png
62 ms
409.png
63 ms
409.png
59 ms
409.png
60 ms
408.png
59 ms
408.png
60 ms
marker-shadow.png
84 ms
408.png
68 ms
408.png
71 ms
409.png
268 ms
409.png
70 ms
sodar2.js
7 ms
runner.html
6 ms
aframe
23 ms
pixel
22 ms
checktimes.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
Image elements do not have [alt] attributes
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
checktimes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
checktimes.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
![]()
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Checktimes.com 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 Checktimes.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
checktimes.com
Open Graph description is not detected on the main page of Check Times. 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: