Tools & Wizards About Us
azperiogroup.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

azperiogroup.com

Arizona Periodontal Group - A Top Periodontist in Phoenix, AZ

Page Load Speed

2.8 sec in total

First Response

39 ms

Resources Loaded

2 sec

Page Rendered

717 ms

azperiogroup.com screenshot

About Website

Click here to check amazing AZ Perio Group content for India. Otherwise, check out these important facts you probably never knew about azperiogroup.com

Visit Dr. Ariel Trujillo, Phoenix periodontist and dental implant surgeon for excellent gum disease treatment. Schedule today.

Visit azperiogroup.com

Key Findings

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

Performance Metrics

azperiogroup.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

azperiogroup.com

39 ms

www.periodontistphoenix.com

713 ms

qvx7uid.css

166 ms

css

72 ms

autoptimize_470414de50c37eb32d371336c5a3a877.css

23 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Azperiogroup.com, 35% (24 requests) were made to Embedsocial.com and 18% (12 requests) were made to Periodontistphoenix.com. The less responsive or slowest element that took the longest time to load (799 ms) relates to the external source Embedsocial.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.3 kB (10%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Azperiogroup.com main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 521.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 105.1 kB

  • Original 128.7 kB
  • After minification 127.4 kB
  • After compression 23.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 105.1 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 435.4 kB
  • After minification 435.4 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. AZ Perio Group images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.0 kB

  • Original 521.7 kB
  • After minification 521.7 kB
  • After compression 515.6 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

-0%

Potential reduce by 164 B

  • Original 53.5 kB
  • After minification 53.5 kB
  • After compression 53.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. Azperiogroup.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (75%)

Requests Now

53

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

azperiogroup.com

azperiogroup.com

39 ms

www.periodontistphoenix.com

www.periodontistphoenix.com

713 ms

qvx7uid.css

qvx7uid.css

166 ms

css

css

72 ms

autoptimize_470414de50c37eb32d371336c5a3a877.css

autoptimize_470414de50c37eb32d371336c5a3a877.css

23 ms

autoptimize_single_431a4faa088252b753ed4d14d321c562.css

autoptimize_single_431a4faa088252b753ed4d14d321c562.css

41 ms

all.css

all.css

64 ms

v4-shims.css

v4-shims.css

75 ms

jquery.min.js

jquery.min.js

43 ms

js

js

106 ms

api.js

api.js

72 ms

wp-polyfill.min.js

wp-polyfill.min.js

47 ms

t.js

t.js

56 ms

conversion.js

conversion.js

74 ms

autoptimize_0799d3fd35d29c7f09f8dba4d52a281d.js

autoptimize_0799d3fd35d29c7f09f8dba4d52a281d.js

51 ms

p.css

p.css

21 ms

stripes.jpg

stripes.jpg

151 ms

ht.js

ht.js

233 ms

ga.js

ga.js

161 ms

gtm.js

gtm.js

146 ms

widget.js

widget.js

238 ms

green-rectanlge-with-outline.png

green-rectanlge-with-outline.png

55 ms

office_reception_.jpg

office_reception_.jpg

123 ms

offset-services-bg-1.jpg

offset-services-bg-1.jpg

54 ms

dental-imaplnts-bg.jpg

dental-imaplnts-bg.jpg

54 ms

Start-your-day-with-a-beautiful-smile-updated.jpg

Start-your-day-with-a-beautiful-smile-updated.jpg

81 ms

94 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff

72 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff

73 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff

95 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXx-p7K4GLs.woff

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff

99 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXx-p7K4GLs.woff

100 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXx-p7K4GLs.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXx-p7K4GLs.woff

104 ms

d

d

23 ms

d

d

66 ms

d

d

152 ms

fa-solid-900.ttf

fa-solid-900.ttf

53 ms

fa-regular-400.ttf

fa-regular-400.ttf

70 ms

__utm.gif

__utm.gif

27 ms

iframe.js

iframe.js

10 ms

iframe-lightbox.min.css

iframe-lightbox.min.css

20 ms

universal-popup.js

universal-popup.js

22 ms

universal-popup.css

universal-popup.css

24 ms

799 ms

18 ms

widget_app_base_1723524817692.js

widget_app_base_1723524817692.js

17 ms

xgRFwgPeJo

xgRFwgPeJo

314 ms

en-US.json

en-US.json

14 ms

widgetviewlive.ff78bfc5.css

widgetviewlive.ff78bfc5.css

6 ms

runtime.3a2e07fa.js

runtime.3a2e07fa.js

7 ms

9500.775d27b4.js

9500.775d27b4.js

13 ms

9376.6c2c332f.js

9376.6c2c332f.js

12 ms

6345.d069dd91.js

6345.d069dd91.js

7 ms

3012.c2b34d21.js

3012.c2b34d21.js

8 ms

4512.61ee3beb.js

4512.61ee3beb.js

10 ms

9140.edef57c1.js

9140.edef57c1.js

11 ms

widgetviewlive.b615b9fb.js

widgetviewlive.b615b9fb.js

11 ms

runtime.4b48a150.js

runtime.4b48a150.js

14 ms

8497.e215fcbf.js

8497.e215fcbf.js

19 ms

829.f55c1725.js

829.f55c1725.js

17 ms

1658.bfd5e0e5.js

1658.bfd5e0e5.js

16 ms

4512.017bd725.js

4512.017bd725.js

18 ms

9557.5cef92bb.js

9557.5cef92bb.js

15 ms

9140.b778626b.js

9140.b778626b.js

18 ms

widgetviewlive.aaf63c41.js

widgetviewlive.aaf63c41.js

27 ms

iframeContent.min.js

iframeContent.min.js

19 ms

Accessibility Review

azperiogroup.com accessibility score

96

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

Links do not have a discernible name

Best Practices

azperiogroup.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

azperiogroup.com SEO score

93

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

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

azperiogroup.com

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