Tools & Wizards About Us
birthdayoncall.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

birthdayoncall.com

Birthday Party Organisers in Delhi Ncr, Gurgaon | Birthday Planners in Delhi

Page Load Speed

12.6 sec in total

First Response

589 ms

Resources Loaded

10.6 sec

Page Rendered

1.3 sec

birthdayoncall.com screenshot

About Website

Visit birthdayoncall.com now to see the best up-to-date Birthday Oncall content for India and also check out these interesting facts you probably never knew about birthdayoncall.com

We at Birthday on Call wish to make your Birthday a sensational event. Based in Delhi, Gurgaon, Noida, we are the best Birthday Party Organisers, Decorators in Delhi & Gurgaon Call Us For Booking.

Visit birthdayoncall.com

Key Findings

We analyzed Birthdayoncall.com page load time and found that the first response time was 589 ms and then it took 12 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

birthdayoncall.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value27.1 s

0/100

25%

SI (Speed Index)

Value13.7 s

1/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

birthdayoncall.com

589 ms

bootstrap.css

800 ms

font-awesome.min.css

657 ms

flaticon.css

551 ms

bootstrap-glyphicons.css

550 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 78% of them (94 requests) were addressed to the original Birthdayoncall.com, 5% (6 requests) were made to Youtube.com and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Birthdayoncall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.3 kB (8%)

Content Size

4.3 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Birthdayoncall.com 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 302.1 kB

  • Original 362.7 kB
  • After minification 328.2 kB
  • After compression 60.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. 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 302.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 16.0 kB

  • Original 3.4 MB
  • After minification 3.4 MB

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. Birthday Oncall images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 6.2 kB

  • Original 404.0 kB
  • After minification 404.0 kB
  • After compression 397.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 5.0 kB

  • Original 113.0 kB
  • After minification 113.0 kB
  • After compression 108.0 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. Birthdayoncall.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (45%)

Requests Now

110

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

birthdayoncall.com

birthdayoncall.com

589 ms

bootstrap.css

bootstrap.css

800 ms

font-awesome.min.css

font-awesome.min.css

657 ms

flaticon.css

flaticon.css

551 ms

bootstrap-glyphicons.css

bootstrap-glyphicons.css

550 ms

css

css

61 ms

css

css

81 ms

style.css

style.css

658 ms

funtime.css

funtime.css

524 ms

owl.carousel.css

owl.carousel.css

1031 ms

prettyPhoto.css

prettyPhoto.css

1082 ms

layerslider.css

layerslider.css

1059 ms

switcher.css

switcher.css

1079 ms

UGc2TpYz8Vc

UGc2TpYz8Vc

148 ms

email-decode.min.js

email-decode.min.js

655 ms

jquery.min.js

jquery.min.js

1316 ms

bootstrap.min.js

bootstrap.min.js

1339 ms

js

js

75 ms

main.js

main.js

1558 ms

jquery.isotope.js

jquery.isotope.js

1607 ms

mc-validate.js

mc-validate.js

1865 ms

plugins.js

plugins.js

1827 ms

contact.js

contact.js

1845 ms

prefixfree.js

prefixfree.js

1808 ms

greensock.js

greensock.js

2326 ms

layerslider.transitions.js

layerslider.transitions.js

2138 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

2569 ms

dmss.js

dmss.js

2358 ms

call.png

call.png

2376 ms

logo.png

logo.png

2370 ms

slide1.jpg

slide1.jpg

2734 ms

sun.png

sun.png

2863 ms

flower.png

flower.png

2862 ms

slide2.jpg

slide2.jpg

2904 ms

bee.png

bee.png

2897 ms

star.png

star.png

3105 ms

slide3.jpg

slide3.jpg

3264 ms

slide4.jpg

slide4.jpg

3353 ms

services.png

services.png

3367 ms

parallaxobject2.png

parallaxobject2.png

3399 ms

1.jpg

1.jpg

3426 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

30 ms

base.js

base.js

57 ms

ad_status.js

ad_status.js

150 ms

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

s9i9Iyk4Y_s1LD6aqz2X9kjqPppJUVpoTsMZDucYENo.js

103 ms

embed.js

embed.js

34 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

37 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

37 ms

id

id

19 ms

2.jpg

2.jpg

3109 ms

Create

Create

136 ms

3.jpg

3.jpg

2998 ms

4.jpg

4.jpg

3239 ms

12.jpg

12.jpg

3235 ms

5.jpg

5.jpg

3255 ms

6.jpg

6.jpg

3303 ms

GenerateIT

GenerateIT

14 ms

8.jpg

8.jpg

3271 ms

9.jpg

9.jpg

3132 ms

10.jpg

10.jpg

3335 ms

11.jpg

11.jpg

3318 ms

parallaxobject1.png

parallaxobject1.png

3115 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

49 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

87 ms

5aUu9_-1phKLFgshYDvh6Vwt5dlKqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5dlKqEp2jg.ttf

114 ms

5aUu9_-1phKLFgshYDvh6Vwt5eFIqEp2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5eFIqEp2jg.ttf

115 ms

Flaticon.woff

Flaticon.woff

3394 ms

fontawesome-webfonte0a5.woff

fontawesome-webfonte0a5.woff

3762 ms

1.jpg

1.jpg

3107 ms

2.jpg

2.jpg

3281 ms

3.jpg

3.jpg

3118 ms

4.jpg

4.jpg

3161 ms

5.jpg

5.jpg

3350 ms

bootstrap.css

bootstrap.css

2737 ms

css

css

20 ms

css

css

57 ms

font-awesome.min.css

font-awesome.min.css

2644 ms

flaticon.css

flaticon.css

2445 ms

bootstrap-glyphicons.css

bootstrap-glyphicons.css

2461 ms

style.css

style.css

2464 ms

funtime.css

funtime.css

2477 ms

log_event

log_event

26 ms

analytics.js

analytics.js

23 ms

counter.js

counter.js

41 ms

owl.carousel.css

owl.carousel.css

2295 ms

collect

collect

145 ms

t.php

t.php

171 ms

skin.css

skin.css

2618 ms

js

js

65 ms

prettyPhoto.css

prettyPhoto.css

2067 ms

layerslider.css

layerslider.css

2082 ms

switcher.css

switcher.css

2068 ms

skin.css

skin.css

2562 ms

6.jpg

6.jpg

2358 ms

7.jpg

7.jpg

1964 ms

8.jpg

8.jpg

2258 ms

9.jpg

9.jpg

2360 ms

10.jpg

10.jpg

2338 ms

11.jpg

11.jpg

2433 ms

12.jpg

12.jpg

2425 ms

13.jpg

13.jpg

2347 ms

14.jpg

14.jpg

2280 ms

15.jpg

15.jpg

2356 ms

16.jpg

16.jpg

2377 ms

17.jpg

17.jpg

2422 ms

18.jpg

18.jpg

2440 ms

parallaxobject3.png

parallaxobject3.png

2334 ms

testimonial1.jpg

testimonial1.jpg

2320 ms

testimonial2.jpg

testimonial2.jpg

2362 ms

testimonial3.jpg

testimonial3.jpg

2396 ms

kids.png

kids.png

3198 ms

bg1.png

bg1.png

2275 ms

hr.png

hr.png

2237 ms

bgcity.png

bgcity.png

2401 ms

lined_paper.png

lined_paper.png

2472 ms

blank.gif

blank.gif

2500 ms

playground.css

playground.css

524 ms

games.css

games.css

508 ms

boxed.css

boxed.css

550 ms

full.css

full.css

538 ms

Accessibility Review

birthdayoncall.com accessibility score

47

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

birthdayoncall.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

birthdayoncall.com SEO score

75

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

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

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 Birthdayoncall.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 Birthdayoncall.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

birthdayoncall.com

Open Graph description is not detected on the main page of Birthday Oncall. 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: