Tools & Wizards About Us
csuf-phoenix.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

csuf-phoenix.com

Now Accepting Telemedicine Visits | Peter Niemczyk, MD FACS: Regenerative Medicine Physician Phoenix, AZ: Center for Sexual & Anti-Aging Medicine

Page Load Speed

4.1 sec in total

First Response

106 ms

Resources Loaded

3.1 sec

Page Rendered

991 ms

csuf-phoenix.com screenshot

About Website

Welcome to csuf-phoenix.com homepage info - get ready to check Csuf Phoenix best content right away, or after learning these important things about csuf-phoenix.com

Now providing Telehealth visits - Book online today! Trusted Regenerative Medicine Physician serving Phoenix, AZ. Contact us at 602-491-9664 or visit us at 9250 N 3rd Street, Suite 2007, Phoenix, AZ 8...

Visit csuf-phoenix.com

Key Findings

We analyzed Csuf-phoenix.com page load time and found that the first response time was 106 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

csuf-phoenix.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value48,390 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.115

86/100

15%

TTI (Time to Interactive)

Value55.6 s

0/100

10%

Network Requests Diagram

csuf-phoenix.com

106 ms

csuf-phoenix.com

196 ms

www.csuf-phoenix.com

372 ms

1950579.png

495 ms

480ad954dc07124d713bf3cc7795bf5b47056f52

676 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 10% of them (5 requests) were addressed to the original Csuf-phoenix.com, 49% (25 requests) were made to Sa1s3optim.patientpop.com and 8% (4 requests) were made to Sa1s3.patientpop.com. The less responsive or slowest element that took the longest time to load (721 ms) relates to the external source Sa1s3optim.patientpop.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.9 kB (37%)

Content Size

1.3 MB

After Optimization

807.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Csuf-phoenix.com main page is 1.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. 45% of websites need less resources to load. Images take 728.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 388.7 kB

  • Original 457.0 kB
  • After minification 433.0 kB
  • After compression 68.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 388.7 kB or 85% of the original size.

Image Optimization

-12%

Potential reduce by 84.2 kB

  • Original 728.2 kB
  • After minification 644.0 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, Csuf Phoenix needs image optimization as it can save up to 84.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

-6%

Potential reduce by 6.0 kB

  • Original 101.0 kB
  • After minification 100.9 kB
  • After compression 95.0 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.

Requests Breakdown

Number of requests can be reduced by 10 (26%)

Requests Now

39

After Optimization

29

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

csuf-phoenix.com

csuf-phoenix.com

106 ms

csuf-phoenix.com

csuf-phoenix.com

196 ms

www.csuf-phoenix.com

www.csuf-phoenix.com

372 ms

1950579.png

1950579.png

495 ms

480ad954dc07124d713bf3cc7795bf5b47056f52

480ad954dc07124d713bf3cc7795bf5b47056f52

676 ms

iframeResizer.min.js

iframeResizer.min.js

527 ms

90509.jpg

90509.jpg

480 ms

85890.jpg

85890.jpg

675 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

326 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

325 ms

RFda8w1V0eDZheqfcyQ4EKRDOzjiPcYnFooOUGCOsRk.woff

RFda8w1V0eDZheqfcyQ4EKRDOzjiPcYnFooOUGCOsRk.woff

308 ms

RFda8w1V0eDZheqfcyQ4EPpCW-pY0asCAalMicFfg1U.woff

RFda8w1V0eDZheqfcyQ4EPpCW-pY0asCAalMicFfg1U.woff

614 ms

RFda8w1V0eDZheqfcyQ4ENRc-2PBzc1NSFKvWogIzAE.woff

RFda8w1V0eDZheqfcyQ4ENRc-2PBzc1NSFKvWogIzAE.woff

619 ms

RFda8w1V0eDZheqfcyQ4EM0NlpArWrQ-mQys31ZNwTE.woff

RFda8w1V0eDZheqfcyQ4EM0NlpArWrQ-mQys31ZNwTE.woff

617 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

324 ms

pp-font-awesome-atomic-subset.woff

pp-font-awesome-atomic-subset.woff

591 ms

d2q878k4s4718u.cloudfront.net

d2q878k4s4718u.cloudfront.net

583 ms

1956648.png

1956648.png

58 ms

1956649.png

1956649.png

51 ms

1956650.png

1956650.png

182 ms

1956651.png

1956651.png

182 ms

1956652.png

1956652.png

179 ms

1956653.png

1956653.png

207 ms

1956654.png

1956654.png

205 ms

1956655.png

1956655.png

205 ms

1956656.png

1956656.png

205 ms

1956658.png

1956658.png

203 ms

1956659.png

1956659.png

263 ms

1956660.png

1956660.png

208 ms

1956661.png

1956661.png

261 ms

1956662.png

1956662.png

261 ms

1956663.png

1956663.png

719 ms

1956664.png

1956664.png

207 ms

1956666.png

1956666.png

721 ms

1956667.png

1956667.png

719 ms

1956668.png

1956668.png

289 ms

1956669.png

1956669.png

288 ms

1956670.png

1956670.png

290 ms

1956671.png

1956671.png

716 ms

chunk-vendors.js

chunk-vendors.js

288 ms

app.js

app.js

198 ms

nr-1216.min.js

nr-1216.min.js

111 ms

16478

16478

343 ms

analytics.js

analytics.js

208 ms

st.js

st.js

218 ms

undefined

undefined

254 ms

78817c6582

78817c6582

212 ms

collect

collect

28 ms

collect

collect

55 ms

379 ms

loader.js

loader.js

48 ms

Accessibility Review

csuf-phoenix.com accessibility score

90

Accessibility Issues

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

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

csuf-phoenix.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

Missing source maps for large first-party JavaScript

SEO Factors

csuf-phoenix.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 Csuf-phoenix.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 Csuf-phoenix.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

csuf-phoenix.com

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