Tools & Wizards About Us
caringforarizona.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

caringforarizona.com

Doctors Specializing in New and Advanced Forms of Medical Care in Phoenix AZ - Find a Doctor in Scottsdale - Caring For Arizona

Page Load Speed

6.1 sec in total

First Response

2.5 sec

Resources Loaded

3.1 sec

Page Rendered

473 ms

caringforarizona.com screenshot

About Website

Welcome to caringforarizona.com homepage info - get ready to check Caring For Arizona best content right away, or after learning these important things about caringforarizona.com

Phoenix area Doctors Specializing in Cancer Treatment, Hormone Replacement, Pain management Plasitc Surgery and more...Watch Listen and Learn...Doctors Caring For You...Caring For Arizona.

Visit caringforarizona.com

Key Findings

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

Performance Metrics

caringforarizona.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value27.9 s

0/100

25%

SI (Speed Index)

Value6.8 s

34/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.335

34/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

caringforarizona.com

2469 ms

wp-emoji-release.min.js

58 ms

vp1_html5.css

67 ms

vp2_html5_bottomPlaylist.css

89 ms

universal_video_player.css

68 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 84% of them (123 requests) were addressed to the original Caringforarizona.com, 8% (12 requests) were made to 0 and 3% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Caringforarizona.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.8 kB (6%)

Content Size

6.3 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Caringforarizona.com main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 109.9 kB

  • Original 130.6 kB
  • After minification 127.6 kB
  • After compression 20.7 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 109.9 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 166.7 kB

  • Original 5.7 MB
  • After minification 5.5 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. Caring For Arizona images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 54.4 kB

  • Original 394.1 kB
  • After minification 394.1 kB
  • After compression 339.7 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 54.4 kB or 14% of the original size.

CSS Optimization

-35%

Potential reduce by 36.9 kB

  • Original 104.6 kB
  • After minification 98.5 kB
  • After compression 67.7 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. Caringforarizona.com needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (55%)

Requests Now

139

After Optimization

62

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

caringforarizona.com

caringforarizona.com

2469 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

58 ms

vp1_html5.css

vp1_html5.css

67 ms

vp2_html5_bottomPlaylist.css

vp2_html5_bottomPlaylist.css

89 ms

universal_video_player.css

universal_video_player.css

68 ms

css

css

25 ms

universal_video_background.css

universal_video_background.css

45 ms

css

css

50 ms

style.css

style.css

347 ms

shortcodes.css

shortcodes.css

91 ms

shortcodes_responsive.css

shortcodes_responsive.css

96 ms

magnific_popup.css

magnific_popup.css

89 ms

ubermenu.min.css

ubermenu.min.css

90 ms

cleanwhite.css

cleanwhite.css

110 ms

font-awesome.min.css

font-awesome.min.css

111 ms

jquery.js

jquery.js

133 ms

jquery-migrate.min.js

jquery-migrate.min.js

112 ms

vp1_html5.js

vp1_html5.js

134 ms

screenfull.min.js

screenfull.min.js

132 ms

vp2_html5_bottomPlaylist.js

vp2_html5_bottomPlaylist.js

133 ms

reflection.js

reflection.js

134 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

155 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

154 ms

froogaloop2.min.js

froogaloop2.min.js

23 ms

universal_video_player.js

universal_video_player.js

155 ms

google_a.js

google_a.js

172 ms

universal_video_background.js

universal_video_background.js

156 ms

style.css

style.css

176 ms

core.min.js

core.min.js

162 ms

widget.min.js

widget.min.js

163 ms

mouse.min.js

mouse.min.js

163 ms

accordion.min.js

accordion.min.js

196 ms

position.min.js

position.min.js

184 ms

menu.min.js

menu.min.js

185 ms

wp-a11y.min.js

wp-a11y.min.js

185 ms

autocomplete.min.js

autocomplete.min.js

185 ms

slider.min.js

slider.min.js

206 ms

tabs.min.js

tabs.min.js

206 ms

sortable.min.js

sortable.min.js

207 ms

js

js

46 ms

draggable.min.js

draggable.min.js

207 ms

droppable.min.js

droppable.min.js

207 ms

selectable.min.js

selectable.min.js

190 ms

datepicker.min.js

datepicker.min.js

180 ms

resizable.min.js

resizable.min.js

181 ms

button.min.js

button.min.js

160 ms

dialog.min.js

dialog.min.js

179 ms

jquery.form.min.js

jquery.form.min.js

177 ms

jquery.color.min.js

jquery.color.min.js

178 ms

imagesloaded.min.js

imagesloaded.min.js

175 ms

masonry.min.js

masonry.min.js

182 ms

jquery.masonry.min.js

jquery.masonry.min.js

180 ms

progressbar.min.js

progressbar.min.js

180 ms

tooltip.min.js

tooltip.min.js

160 ms

effect.min.js

effect.min.js

160 ms

effect-blind.min.js

effect-blind.min.js

197 ms

effect-bounce.min.js

effect-bounce.min.js

180 ms

effect-clip.min.js

effect-clip.min.js

180 ms

effect-drop.min.js

effect-drop.min.js

160 ms

effect-explode.min.js

effect-explode.min.js

160 ms

effect-fade.min.js

effect-fade.min.js

180 ms

effect-fold.min.js

effect-fold.min.js

180 ms

effect-highlight.min.js

effect-highlight.min.js

164 ms

effect-pulsate.min.js

effect-pulsate.min.js

161 ms

effect-size.min.js

effect-size.min.js

258 ms

effect-scale.min.js

effect-scale.min.js

255 ms

effect-shake.min.js

effect-shake.min.js

254 ms

effect-slide.min.js

effect-slide.min.js

235 ms

effect-transfer.min.js

effect-transfer.min.js

234 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

237 ms

custom.js

custom.js

235 ms

jquery.fitvids.js

jquery.fitvids.js

225 ms

waypoints.min.js

waypoints.min.js

215 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

215 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

229 ms

ubermenu.min.js

ubermenu.min.js

214 ms

wp-embed.min.js

wp-embed.min.js

194 ms

script.js

script.js

193 ms

analytics.js

analytics.js

65 ms

CAZLogo.png

CAZLogo.png

79 ms

frontpage.jpg

frontpage.jpg

175 ms

frontslkde9.png

frontslkde9.png

125 ms

facebook.png

facebook.png

120 ms

petelin.png

petelin.png

175 ms

drwilsonlg.png

drwilsonlg.png

177 ms

wolinlarge.png

wolinlarge.png

120 ms

simoncinilg.png

simoncinilg.png

171 ms

bottombox.png

bottombox.png

176 ms

drpetelin1.png

drpetelin1.png

54 ms

rosesm.png

rosesm.png

52 ms

drwilson.png

drwilson.png

53 ms

drcraig.png

drcraig.png

55 ms

cohensm.png

cohensm.png

55 ms

drwebb.png

drwebb.png

65 ms

bartelssm.png

bartelssm.png

65 ms

drpetelin.png

drpetelin.png

119 ms

drmccracken.png

drmccracken.png

67 ms

drwolin1.png

drwolin1.png

66 ms

rubinsmall.png

rubinsmall.png

116 ms

jeffsm.png

jeffsm.png

121 ms

lieberman.png

lieberman.png

119 ms

alexandersm.png

alexandersm.png

120 ms

larsonsm.png

larsonsm.png

120 ms

dr10.png

dr10.png

121 ms

kellysmal.png

kellysmal.png

169 ms

drali.png

drali.png

121 ms

drdaiza.png

drdaiza.png

121 ms

leesm.png

leesm.png

121 ms

dr4.png

dr4.png

122 ms

cannata.png

cannata.png

129 ms

dr7.png

dr7.png

127 ms

dr3.png

dr3.png

126 ms

dr9.png

dr9.png

127 ms

dr2.png

dr2.png

126 ms

anadsm.png

anadsm.png

130 ms

jonathansm.png

jonathansm.png

126 ms

nuargalgsm.png

nuargalgsm.png

126 ms

dr5.png

dr5.png

127 ms

dr6.png

dr6.png

134 ms

dr1.png

dr1.png

126 ms

farrelsmall.png

farrelsmall.png

131 ms

dr8.png

dr8.png

132 ms

smithsm.png

smithsm.png

132 ms

a12s.png

a12s.png

143 ms

a10s.png

a10s.png

132 ms

a9s.png

a9s.png

143 ms

dr11.png

dr11.png

165 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

11 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

60 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

61 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

62 ms

ETmodules_v2_4.ttf

ETmodules_v2_4.ttf

146 ms

a8s.png

a8s.png

136 ms

a7s.png

a7s.png

144 ms

a5s.png

a5s.png

169 ms

a4s.png

a4s.png

153 ms

a3s.png

a3s.png

109 ms

banner2.png

banner2.png

142 ms

spotlight2.png

spotlight2.png

140 ms

webbback.png

webbback.png

94 ms

a2s.png

a2s.png

107 ms

awards-1.jpg

awards-1.jpg

131 ms

rose.png

rose.png

135 ms

bartelslg.png

bartelslg.png

122 ms

piwik.js

piwik.js

133 ms

Accessibility Review

caringforarizona.com accessibility score

78

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

caringforarizona.com best practices score

75

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

Page has valid source maps

SEO Factors

caringforarizona.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 doesn't use 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 Caringforarizona.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 Caringforarizona.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

caringforarizona.com

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