Tools & Wizards About Us
houston.baps.org screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

houston.baps.org

BAPS Shri Swaminarayan Mandir, Houston

Page Load Speed

3.6 sec in total

First Response

1.3 sec

Resources Loaded

1.9 sec

Page Rendered

434 ms

houston.baps.org screenshot

About Website

Click here to check amazing Houston BAPS content for India. Otherwise, check out these important facts you probably never knew about houston.baps.org

BAPS Shri Swaminarayan Sanstha

Visit houston.baps.org

Key Findings

We analyzed Houston.baps.org page load time and found that the first response time was 1.3 sec and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

houston.baps.org performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.434

21/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

houston

1331 ms

css

24 ms

jquery-ui.css

34 ms

csshandler.ashx

100 ms

theme.css

63 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Houston.baps.org, 5% (3 requests) were made to Ajax.googleapis.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Baps.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.1 kB (19%)

Content Size

2.4 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Houston.baps.org main page is 2.4 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 47.4 kB

  • Original 61.8 kB
  • After minification 54.6 kB
  • After compression 14.3 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 7.2 kB, which is 12% 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 47.4 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 122.0 kB

  • Original 1.9 MB
  • After minification 1.8 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. Houston BAPS images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 221.0 kB

  • Original 317.2 kB
  • After minification 293.7 kB
  • After compression 96.2 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 221.0 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 65.7 kB

  • Original 81.5 kB
  • After minification 80.3 kB
  • After compression 15.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. Houston.baps.org needs all CSS files to be minified and compressed as it can save up to 65.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (32%)

Requests Now

53

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

houston

houston

1331 ms

css

css

24 ms

jquery-ui.css

jquery-ui.css

34 ms

csshandler.ashx

csshandler.ashx

100 ms

theme.css

theme.css

63 ms

WebResource.axd

WebResource.axd

86 ms

BAPScombined.js

BAPScombined.js

72 ms

jquery.min.js

jquery.min.js

18 ms

jquery-ui.min.js

jquery-ui.min.js

40 ms

ScriptResource.axd

ScriptResource.axd

142 ms

ScriptResource.axd

ScriptResource.axd

140 ms

ScriptResource.axd

ScriptResource.axd

83 ms

style.css

style.css

79 ms

scripts.js

scripts.js

82 ms

analytics.js

analytics.js

9 ms

bgwide.jpg

bgwide.jpg

214 ms

Houston_diwali2015_01_005.jpg

Houston_diwali2015_01_005.jpg

274 ms

Houston_Kids_Diwali.jpg

Houston_Kids_Diwali.jpg

274 ms

Houston_CampusDiwali.jpg

Houston_CampusDiwali.jpg

212 ms

BAPS%20Houston%20Mandir%20Moods%2005f.jpg

BAPS%20Houston%20Mandir%20Moods%2005f.jpg

203 ms

3636-houston.jpg

3636-houston.jpg

236 ms

collect

collect

14 ms

superfish.js

superfish.js

207 ms

houston_mahila_psmjj_2015_04.JPG

houston_mahila_psmjj_2015_04.JPG

245 ms

Houston_PSMJJ_2015_19.jpg

Houston_PSMJJ_2015_19.jpg

244 ms

Houston_CampusDiwali2015_00001_001.jpg

Houston_CampusDiwali2015_00001_001.jpg

249 ms

Houston_diwali2015_33.jpg

Houston_diwali2015_33.jpg

251 ms

Houston_Kids_Diwali_2015_16.JPG

Houston_Kids_Diwali_2015_16.JPG

249 ms

Houston_Mahila_Janmashtami2015_01.JPG

Houston_Mahila_Janmashtami2015_01.JPG

251 ms

Housoton_Janmashtami2015_02.jpg

Housoton_Janmashtami2015_02.jpg

251 ms

Fuldol-Flyer-2016-Web.jpg

Fuldol-Flyer-2016-Web.jpg

251 ms

BAPS-WC-2016-Web.jpg

BAPS-WC-2016-Web.jpg

292 ms

20160313A_homethumb.jpg

20160313A_homethumb.jpg

294 ms

36SchoolHome.jpg

36SchoolHome.jpg

293 ms

Thumb_1301_Homepage%20Photo-f.jpg

Thumb_1301_Homepage%20Photo-f.jpg

291 ms

thumb_21mandirss.jpg

thumb_21mandirss.jpg

294 ms

Thumb_3636-houston.jpg

Thumb_3636-houston.jpg

295 ms

Thumb_43la1.jpg

Thumb_43la1.jpg

294 ms

Thumb_865BAPSShriSwaminarayan%20Mandir%20Robbinsville.JPG

Thumb_865BAPSShriSwaminarayan%20Mandir%20Robbinsville.JPG

296 ms

Thumb_75toronto-mandir.jpg

Thumb_75toronto-mandir.jpg

297 ms

feed.png

feed.png

294 ms

headerbg.jpg

headerbg.jpg

194 ms

bapslogo.jpg

bapslogo.jpg

193 ms

menunav_bg.jpg

menunav_bg.jpg

207 ms

arrowdown.png

arrowdown.png

203 ms

all.js

all.js

36 ms

widgets.js

widgets.js

149 ms

ga.js

ga.js

33 ms

silde-nav.png

silde-nav.png

71 ms

slide-pp.png

slide-pp.png

72 ms

116 ms

xd_arbiter.php

xd_arbiter.php

46 ms

xd_arbiter.php

xd_arbiter.php

56 ms

gbcombined.js

gbcombined.js

28 ms

gb_scripts.js

gb_scripts.js

18 ms

Accessibility Review

houston.baps.org accessibility score

69

Accessibility Issues

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

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.

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

Best Practices

houston.baps.org 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

houston.baps.org SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

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

    N/A

  • Encoding

    UTF-8

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

houston.baps.org

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