Tools & Wizards About Us
aspe.org screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

aspe.org

ASPE - American Society of Plumbing Engineers

Page Load Speed

2.2 sec in total

First Response

219 ms

Resources Loaded

1.8 sec

Page Rendered

104 ms

aspe.org screenshot

About Website

Click here to check amazing ASPE content for United States. Otherwise, check out these important facts you probably never knew about aspe.org

ASPE is the only international organization dedicated to promoting the plumbing engineering profession. Learn more at aspe.org.

Visit aspe.org

Key Findings

We analyzed Aspe.org page load time and found that the first response time was 219 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

aspe.org performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

aspe.org

219 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

56 ms

css_JKvJ0XzKVIrddZG2JypV9DL9uYWig5L6ivvzF7VR-nM.css

68 ms

css_DvuFlw96TNxuqOiHcRVOpahwTocK5LxIm0R1FQupuC4.css

71 ms

css_kBhlbecH1iTrpa_nWPhbfeM_hPfR51I-_jpikWMRcd4.css

73 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 91% of them (50 requests) were addressed to the original Aspe.org, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Aspe.org.

Page Optimization Overview & Recommendations

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

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aspe.org 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. 35% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 34.9 kB

  • Original 44.3 kB
  • After minification 42.4 kB
  • After compression 9.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.9 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 227.2 kB

  • Original 2.0 MB
  • After minification 1.7 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. Obviously, ASPE needs image optimization as it can save up to 227.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 121.2 kB

  • Original 196.0 kB
  • After minification 150.2 kB
  • After compression 74.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 121.2 kB or 62% of the original size.

CSS Optimization

-79%

Potential reduce by 50.3 kB

  • Original 63.6 kB
  • After minification 58.1 kB
  • After compression 13.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. Aspe.org needs all CSS files to be minified and compressed as it can save up to 50.3 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

53

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aspe.org

aspe.org

219 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

56 ms

css_JKvJ0XzKVIrddZG2JypV9DL9uYWig5L6ivvzF7VR-nM.css

css_JKvJ0XzKVIrddZG2JypV9DL9uYWig5L6ivvzF7VR-nM.css

68 ms

css_DvuFlw96TNxuqOiHcRVOpahwTocK5LxIm0R1FQupuC4.css

css_DvuFlw96TNxuqOiHcRVOpahwTocK5LxIm0R1FQupuC4.css

71 ms

css_kBhlbecH1iTrpa_nWPhbfeM_hPfR51I-_jpikWMRcd4.css

css_kBhlbecH1iTrpa_nWPhbfeM_hPfR51I-_jpikWMRcd4.css

73 ms

nice_menus.css

nice_menus.css

78 ms

css

css

25 ms

jquery.min.js

jquery.min.js

6 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

1055 ms

js_dIVeFeR1fd2J80S5lsKnQ7bHHaKECVJsJmNx3d9BDX8.js

js_dIVeFeR1fd2J80S5lsKnQ7bHHaKECVJsJmNx3d9BDX8.js

118 ms

js_FvBWezKhsGxJU-Yi41qvYAlpXctdNNR7mIzff4prZrg.js

js_FvBWezKhsGxJU-Yi41qvYAlpXctdNNR7mIzff4prZrg.js

98 ms

js_2tEyj971V0p7IxdaBrTZtpn3CvR1qlj8TxZjXUmo38c.js

js_2tEyj971V0p7IxdaBrTZtpn3CvR1qlj8TxZjXUmo38c.js

99 ms

js_a_XWH2S1EQaU85ypMDyQGiUfzPFez1IOZKxHnhGkv3E.js

js_a_XWH2S1EQaU85ypMDyQGiUfzPFez1IOZKxHnhGkv3E.js

98 ms

js_SLkb7SMhptwh-2izWJjBOtYbcN3_vY_fDS5jdLFHaOo.js

js_SLkb7SMhptwh-2izWJjBOtYbcN3_vY_fDS5jdLFHaOo.js

99 ms

analytics.js

analytics.js

90 ms

aspe-logo166Ht_0.png

aspe-logo166Ht_0.png

70 ms

arrow-down.png

arrow-down.png

68 ms

arrow-right.png

arrow-right.png

71 ms

MentoringProgram.png

MentoringProgram.png

72 ms

2016convention_slider2.png

2016convention_slider2.png

103 ms

home_page_slider_ch_challenge_0.png

home_page_slider_ch_challenge_0.png

178 ms

steele_award_slider_2.png

steele_award_slider_2.png

364 ms

ASPEJournal_grey.jpg

ASPEJournal_grey.jpg

203 ms

standards.jpg

standards.jpg

242 ms

rf.jpg

rf.jpg

106 ms

pe.jpg

pe.jpg

172 ms

ceu.jpg

ceu.jpg

247 ms

Morris_FINAL.png

Morris_FINAL.png

208 ms

QuantumFlo_FINAL.jpg

QuantumFlo_FINAL.jpg

215 ms

Rada_FINAL.jpg

Rada_FINAL.jpg

237 ms

Navien_FINAL.jpg

Navien_FINAL.jpg

243 ms

NSF_FINAL.jpg

NSF_FINAL.jpg

252 ms

watts_.jpg

watts_.jpg

271 ms

Zurn%20FINAL.jpg

Zurn%20FINAL.jpg

275 ms

Culligan%20%282%29.jpg

Culligan%20%282%29.jpg

351 ms

BradfordWhite%20%282%29.jpg

BradfordWhite%20%282%29.jpg

351 ms

CSA%20%282%29.jpg

CSA%20%282%29.jpg

355 ms

ECCO_FINAL.jpg

ECCO_FINAL.jpg

305 ms

Uponor%20%282%29.jpg

Uponor%20%282%29.jpg

346 ms

Lubrizol%20%282%29.jpg

Lubrizol%20%282%29.jpg

376 ms

IAPMO%20%282%29.jpg

IAPMO%20%282%29.jpg

418 ms

Viega%20%282%29.jpg

Viega%20%282%29.jpg

423 ms

HoldRite%20%282%29.jpg

HoldRite%20%282%29.jpg

427 ms

Copper%20%282%29.jpg

Copper%20%282%29.jpg

431 ms

Charlotte%20%282%29.jpg

Charlotte%20%282%29.jpg

436 ms

webinar-button-no-border.png

webinar-button-no-border.png

410 ms

IETS_banner.png

IETS_banner.png

444 ms

cart-empty.png

cart-empty.png

451 ms

bullet-arrow-down.gif

bullet-arrow-down.gif

455 ms

logo_WPC.jpg

logo_WPC.jpg

461 ms

FJNab1jzp1t7ctjNl8ugHKCWcynf_cDxXwCLxiixG1c.ttf

FJNab1jzp1t7ctjNl8ugHKCWcynf_cDxXwCLxiixG1c.ttf

11 ms

podiologo.jpg

podiologo.jpg

464 ms

collect

collect

13 ms

loading.gif

loading.gif

407 ms

arrows.png

arrows.png

414 ms

Accessibility Review

aspe.org accessibility score

96

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-hidden="true"] elements contain focusable descendents

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

aspe.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

aspe.org SEO score

93

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

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 Aspe.org 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 Aspe.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

aspe.org

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