Tools & Wizards About Us
m.mobilepanchang.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

m.mobilepanchang.com

Online Panchang, Panchangam and Hindu Calendar for the world

Page Load Speed

7.3 sec in total

First Response

1.8 sec

Resources Loaded

5.2 sec

Page Rendered

298 ms

m.mobilepanchang.com screenshot

About Website

Visit m.mobilepanchang.com now to see the best up-to-date M Mobile Panchang content for India and also check out these interesting facts you probably never knew about m.mobilepanchang.com

This page provides daily panchang (also called as panchangam) for most cities in the world. This page also lists countdown timer for upcoming fasting days and festivals for most cities in the world.

Visit m.mobilepanchang.com

Key Findings

We analyzed M.mobilepanchang.com page load time and found that the first response time was 1.8 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

m.mobilepanchang.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value5,040 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.219

57/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

m.mobilepanchang.com

1796 ms

www.drikpanchang.com

676 ms

dkcommonstyle.css

78 ms

dp-jquery-ui.css

101 ms

dp-home.css

102 ms

Our browser made a total of 175 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original M.mobilepanchang.com, 27% (47 requests) were made to Static.drikpanchang.com and 8% (14 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain M.mobilepanchang.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (55%)

Content Size

2.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.mobilepanchang.com main page is 2.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. 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. Javascripts take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 116.8 kB

  • Original 148.7 kB
  • After minification 147.9 kB
  • After compression 31.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 116.8 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 25.3 kB

  • Original 240.9 kB
  • After minification 215.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. Obviously, M Mobile Panchang needs image optimization as it can save up to 25.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 1.1 MB

  • Original 1.9 MB
  • After minification 1.9 MB
  • After compression 791.6 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 1.1 MB or 58% of the original size.

CSS Optimization

-81%

Potential reduce by 44.7 kB

  • Original 55.0 kB
  • After minification 48.1 kB
  • After compression 10.3 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. M.mobilepanchang.com needs all CSS files to be minified and compressed as it can save up to 44.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 87 (54%)

Requests Now

160

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Mobile Panchang. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

m.mobilepanchang.com

m.mobilepanchang.com

1796 ms

www.drikpanchang.com

www.drikpanchang.com

676 ms

dkcommonstyle.css

dkcommonstyle.css

78 ms

dp-jquery-ui.css

dp-jquery-ui.css

101 ms

dp-home.css

dp-home.css

102 ms

jquery.min.js

jquery.min.js

4 ms

jquery-ui.min.js

jquery-ui.min.js

8 ms

panchang-jquery.js

panchang-jquery.js

243 ms

dp-digi-clk.js

dp-digi-clk.js

97 ms

dp-city-search.js

dp-city-search.js

98 ms

adsbygoogle.js

adsbygoogle.js

4 ms

nmedianet.js

nmedianet.js

130 ms

pinit.js

pinit.js

10 ms

dp-clock.php

dp-clock.php

267 ms

analytics.js

analytics.js

21 ms

middle_background.jpg

middle_background.jpg

44 ms

head_shadow.jpg

head_shadow.jpg

186 ms

digi_frame_simple.png

digi_frame_simple.png

44 ms

donation_icon.png

donation_icon.png

16 ms

signin_base.png

signin_base.png

44 ms

www_drikpanchang.png

www_drikpanchang.png

45 ms

title_bg.jpg

title_bg.jpg

45 ms

deepakl.gif

deepakl.gif

47 ms

deepakr.gif

deepakr.gif

59 ms

dp_search.png

dp_search.png

46 ms

hindi_native.png

hindi_native.png

58 ms

empty-tab.png

empty-tab.png

59 ms

globe.png

globe.png

67 ms

panchang.png

panchang.png

67 ms

calendar.png

calendar.png

135 ms

kundali.png

kundali.png

77 ms

muhurat.png

muhurat.png

134 ms

gallery.png

gallery.png

135 ms

rashi.png

rashi.png

136 ms

kalash.png

kalash.png

136 ms

upavas.png

upavas.png

150 ms

solar_system.png

solar_system.png

151 ms

lyrics.png

lyrics.png

151 ms

puja_thali.png

puja_thali.png

150 ms

swastik.png

swastik.png

252 ms

shree.png

shree.png

182 ms

star.png

star.png

182 ms

om.png

om.png

181 ms

yantra.png

yantra.png

180 ms

marriage.png

marriage.png

207 ms

mobile_apps.png

mobile_apps.png

207 ms

vrat_katha.png

vrat_katha.png

207 ms

anchor_kalash.png

anchor_kalash.png

208 ms

dp_logo_panditji.png

dp_logo_panditji.png

206 ms

gp_vertical.png

gp_vertical.png

245 ms

fb_vertical.png

fb_vertical.png

237 ms

ca-pub-7521580084298365.js

ca-pub-7521580084298365.js

43 ms

zrt_lookup.html

zrt_lookup.html

86 ms

show_ads_impl.js

show_ads_impl.js

49 ms

linkid.js

linkid.js

11 ms

centerpattern.jpg

centerpattern.jpg

209 ms

collect

collect

15 ms

collect

collect

102 ms

ads

ads

164 ms

osd.js

osd.js

42 ms

px.gif

px.gif

35 ms

px.gif

px.gif

169 ms

browserfp.min.js

browserfp.min.js

200 ms

bping.php

bping.php

72 ms

jstag

jstag

70 ms

rtbspub

rtbspub

57 ms

fcmdynet.js

fcmdynet.js

194 ms

gpt.js

gpt.js

49 ms

ads

ads

117 ms

checksync.php

checksync.php

47 ms

ga-audiences

ga-audiences

97 ms

ads

ads

118 ms

pubads_impl_147.js

pubads_impl_147.js

33 ms

cksync.html

cksync.html

38 ms

acj

acj

50 ms

cksync.php

cksync.php

36 ms

container.html

container.html

13 ms

analytics.js

analytics.js

28 ms

score_plain_no_change.js

score_plain_no_change.js

32 ms

abg.js

abg.js

51 ms

m_window_focus_non_hydra.js

m_window_focus_non_hydra.js

532 ms

osd_listener.js

osd_listener.js

532 ms

m_qs_click_protection.js

m_qs_click_protection.js

539 ms

html

html

594 ms

powered-by-google.png

powered-by-google.png

500 ms

8646052541948665570

8646052541948665570

539 ms

14634943584314564633

14634943584314564633

539 ms

10667946647809175745

10667946647809175745

541 ms

mediamain.html

mediamain.html

731 ms

hmmaster.js

hmmaster.js

528 ms

bottom_shadow.jpg

bottom_shadow.jpg

531 ms

close.png

close.png

532 ms

close.png

close.png

528 ms

beacon_img

beacon_img

586 ms

cenw.js

cenw.js

136 ms

ptmd

ptmd

138 ms

ptmd

ptmd

137 ms

ptmd

ptmd

139 ms

ptmd

ptmd

139 ms

ptmd

ptmd

137 ms

transparent.png

transparent.png

56 ms

sdk.js

sdk.js

45 ms

plusone.js

plusone.js

120 ms

widgets.js

widgets.js

50 ms

ui-bg_flat_30_FFC15E_40x100.png

ui-bg_flat_30_FFC15E_40x100.png

86 ms

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

8K3Zg6NpZGSge3qWJUIO0OW0x1SCW4IXoAiImY1mvc4.js

56 ms

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

80 ms

d68115297f24f2845da8516b7ec85832.gif

d68115297f24f2845da8516b7ec85832.gif

146 ms

pinit_main.js

pinit_main.js

49 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

28 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

74 ms

sharebutton

sharebutton

103 ms

fastbutton

fastbutton

102 ms

page

page

170 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

49 ms

0sTQzbapM8j.js

0sTQzbapM8j.js

101 ms

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

25 ms

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

53 ms

postmessageRelay

postmessageRelay

79 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

15 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

26 ms

unsupportedbrowser

unsupportedbrowser

210 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

49 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

86 ms

rs=AGLTcCO-_eQ7o1FulFxZ-KCwqhQMrsSSpA

rs=AGLTcCO-_eQ7o1FulFxZ-KCwqhQMrsSSpA

5 ms

ptmd

ptmd

22 ms

971028622-postmessagerelay.js

971028622-postmessagerelay.js

179 ms

rpc:shindig_random.js

rpc:shindig_random.js

113 ms

photo.jpg

photo.jpg

152 ms

drikpanchang_cover.jpg

drikpanchang_cover.jpg

174 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

54 ms

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA

18 ms

rs=AGLTcCMe922Q6xmOdBJBl7J6I2ZmcHJH2g

rs=AGLTcCMe922Q6xmOdBJBl7J6I2ZmcHJH2g

53 ms

ads

ads

304 ms

rs=AGLTcCMe922Q6xmOdBJBl7J6I2ZmcHJH2g

rs=AGLTcCMe922Q6xmOdBJBl7J6I2ZmcHJH2g

46 ms

ptmd

ptmd

26 ms

ptmd

ptmd

26 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

jstag

jstag

20 ms

checksync.php

checksync.php

25 ms

acj

acj

10 ms

unsupportedbrowser

unsupportedbrowser

50 ms

unsupportedbrowser

unsupportedbrowser

48 ms

pd

pd

7 ms

f3019eb9-d240-a918-6f82-1d01da8266f0

f3019eb9-d240-a918-6f82-1d01da8266f0

38 ms

cfcm.ashx

cfcm.ashx

191 ms

openx

openx

6 ms

pixel

pixel

14 ms

openx

openx

3 ms

sd

sd

4 ms

sd

sd

3 ms

getuid

getuid

51 ms

sd

sd

20 ms

cksync.php

cksync.php

95 ms

jot.html

jot.html

16 ms

sd

sd

4 ms

sd

sd

10 ms

getuid

getuid

5 ms

sd

sd

5 ms

sd

sd

5 ms

osd.js

osd.js

6 ms

3652

3652

778 ms

cookie_push.html

cookie_push.html

9 ms

ext.js

ext.js

9 ms

m

m

109 ms

rtblog.php

rtblog.php

209 ms

log

log

124 ms

cksync.php

cksync.php

14 ms

pixel

pixel

15 ms

activeview

activeview

13 ms

activeview

activeview

12 ms

7a8f9f5f3707aaa8384a672bac15da17.gif

7a8f9f5f3707aaa8384a672bac15da17.gif

216 ms

ic

ic

4 ms

pixel

pixel

13 ms

1x1

1x1

3 ms

Accessibility Review

m.mobilepanchang.com accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

m.mobilepanchang.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

m.mobilepanchang.com SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.mobilepanchang.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 M.mobilepanchang.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.

Social Sharing Optimization

m.mobilepanchang.com

Open Graph data is detected on the main page of M Mobile Panchang. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: