Tools & Wizards About Us
dialcode.org screenshot

Report Summary

  • 96

    Performance

    Renders faster than
    94% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

dialcode.org

Dial Codes for Cities round the World - City Phone Dial Code Widgets - World Telephone Dial Codes

Page Load Speed

2.1 sec in total

First Response

234 ms

Resources Loaded

1.7 sec

Page Rendered

201 ms

dialcode.org screenshot

About Website

Welcome to dialcode.org homepage info - get ready to check Dial Code best content for India right away, or after learning these important things about dialcode.org

World dial code information. Country dial and city area codes for World Dial code widgets for World

Visit dialcode.org

Key Findings

We analyzed Dialcode.org page load time and found that the first response time was 234 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

dialcode.org performance score

96

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

99/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

dialcode.org

234 ms

style1.css

10 ms

show_ads.js

24 ms

clock.php

208 ms

clock.php

391 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 71% of them (97 requests) were addressed to the original Dialcode.org, 7% (9 requests) were made to Static.xx.fbcdn.net and 5% (7 requests) were made to Localtimes.info. The less responsive or slowest element that took the longest time to load (639 ms) relates to the external source Static.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.4 kB (56%)

Content Size

170.4 kB

After Optimization

75.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dialcode.org main page is 170.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 86.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 74.7 kB

  • Original 86.8 kB
  • After minification 86.0 kB
  • After compression 12.1 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 74.7 kB or 86% of the original size.

Image Optimization

-19%

Potential reduce by 11.3 kB

  • Original 58.9 kB
  • After minification 47.6 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, Dial Code needs image optimization as it can save up to 11.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 1.8 kB

  • Original 15.7 kB
  • After minification 15.5 kB
  • After compression 13.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 1.8 kB or 12% of the original size.

CSS Optimization

-84%

Potential reduce by 7.5 kB

  • Original 9.0 kB
  • After minification 8.0 kB
  • After compression 1.4 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. Dialcode.org needs all CSS files to be minified and compressed as it can save up to 7.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 121 (90%)

Requests Now

134

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 134 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dial Code. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

dialcode.org

dialcode.org

234 ms

style1.css

style1.css

10 ms

show_ads.js

show_ads.js

24 ms

clock.php

clock.php

208 ms

clock.php

clock.php

391 ms

clock.php

clock.php

402 ms

clock.php

clock.php

407 ms

clock.php

clock.php

316 ms

clock.php

clock.php

403 ms

clock.php

clock.php

401 ms

dialcode_from.php

dialcode_from.php

196 ms

fx-rates.php

fx-rates.php

31 ms

counter.js

counter.js

28 ms

dialcode_r1.png

dialcode_r1.png

25 ms

find.gif

find.gif

24 ms

de.png

de.png

33 ms

fr.png

fr.png

55 ms

gb.png

gb.png

25 ms

ru.png

ru.png

27 ms

it.png

it.png

26 ms

es.png

es.png

27 ms

se.png

se.png

28 ms

at.png

at.png

28 ms

ie.png

ie.png

30 ms

gr.png

gr.png

28 ms

pt.png

pt.png

30 ms

tr.png

tr.png

32 ms

ua.png

ua.png

33 ms

no.png

no.png

32 ms

dk.png

dk.png

30 ms

ch.png

ch.png

31 ms

pl.png

pl.png

37 ms

cz.png

cz.png

33 ms

nl.png

nl.png

33 ms

fi.png

fi.png

44 ms

hu.png

hu.png

34 ms

ro.png

ro.png

35 ms

by.png

by.png

49 ms

be.png

be.png

49 ms

bg.png

bg.png

47 ms

sk.png

sk.png

50 ms

rs.png

rs.png

54 ms

hr.png

hr.png

51 ms

ee.png

ee.png

52 ms

cy.png

cy.png

52 ms

mk.png

mk.png

57 ms

za.png

za.png

56 ms

zrt_lookup.html

zrt_lookup.html

109 ms

show_ads_impl.js

show_ads_impl.js

47 ms

dz.png

dz.png

114 ms

eg.png

eg.png

42 ms

ma.png

ma.png

105 ms

tn.png

tn.png

105 ms

ng.png

ng.png

105 ms

ke.png

ke.png

105 ms

bw.png

bw.png

107 ms

cd.png

cd.png

105 ms

cn.png

cn.png

109 ms

in.png

in.png

104 ms

jp.png

jp.png

109 ms

id.png

id.png

104 ms

ph.png

ph.png

104 ms

kr.png

kr.png

104 ms

kz.png

kz.png

105 ms

sa.png

sa.png

106 ms

th.png

th.png

106 ms

tw.png

tw.png

104 ms

ir.png

ir.png

104 ms

mn.png

mn.png

109 ms

tm.png

tm.png

103 ms

my.png

my.png

109 ms

il.png

il.png

102 ms

vn.png

vn.png

97 ms

uz.png

uz.png

93 ms

pk.png

pk.png

92 ms

om.png

om.png

93 ms

sy.png

sy.png

93 ms

kp.png

kp.png

92 ms

ye.png

ye.png

92 ms

ae.png

ae.png

91 ms

bd.png

bd.png

89 ms

iq.png

iq.png

91 ms

us.png

us.png

88 ms

mx.png

mx.png

87 ms

ads

ads

185 ms

ca.png

ca.png

29 ms

osd.js

osd.js

35 ms

do.png

do.png

27 ms

hn.png

hn.png

30 ms

cu.png

cu.png

25 ms

bs.png

bs.png

24 ms

gt.png

gt.png

23 ms

cr.png

cr.png

26 ms

br.png

br.png

25 ms

ar.png

ar.png

25 ms

ve.png

ve.png

24 ms

cl.png

cl.png

40 ms

pe.png

pe.png

37 ms

co.png

co.png

37 ms

bo.png

bo.png

41 ms

ec.png

ec.png

37 ms

uy.png

uy.png

36 ms

py.png

py.png

40 ms

au.png

au.png

35 ms

nz.png

nz.png

36 ms

pg.png

pg.png

35 ms

fj.png

fj.png

35 ms

as.png

as.png

36 ms

topmenu.png

topmenu.png

34 ms

m_js_controller.js

m_js_controller.js

23 ms

abg.js

abg.js

44 ms

favicon

favicon

77 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

74 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

32 ms

s

s

18 ms

x_button_blue2.png

x_button_blue2.png

8 ms

au.png

au.png

10 ms

ico_twitter3.gif

ico_twitter3.gif

7 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

10 ms

ch.png

ch.png

8 ms

eu.png

eu.png

9 ms

gb.png

gb.png

14 ms

hk.png

hk.png

8 ms

jp.png

jp.png

9 ms

fb.ico

fb.ico

169 ms

t.php

t.php

52 ms

like.php

like.php

115 ms

_JWi8n0NIf6.css

_JWi8n0NIf6.css

287 ms

Xg5YhPIEtBP.css

Xg5YhPIEtBP.css

355 ms

AdP_CKHZFBh.css

AdP_CKHZFBh.css

422 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

619 ms

TuuohdynnB6.js

TuuohdynnB6.js

488 ms

d6RcVOf4_V3.js

d6RcVOf4_V3.js

639 ms

phKJLmGTCBO.js

phKJLmGTCBO.js

639 ms

Bw8qRoQ9D-v.js

Bw8qRoQ9D-v.js

69 ms

Xz08Qlfw8qz.js

Xz08Qlfw8qz.js

202 ms

ui

ui

66 ms

Accessibility Review

dialcode.org accessibility score

56

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

dialcode.org best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dialcode.org SEO score

87

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

dialcode.org

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: