Tools & Wizards About Us
dixonphone.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

dixonphone.com

Dixon Phone Place, Inc | Phone Equipment Company Indianapolis IN

Page Load Speed

2.6 sec in total

First Response

116 ms

Resources Loaded

2.3 sec

Page Rendered

165 ms

dixonphone.com screenshot

About Website

Click here to check amazing Dixon Phone content. Otherwise, check out these important facts you probably never knew about dixonphone.com

Call 317-251-3504 when looking for a dependable phone equipment company in Indianapolis IN. Dixon Phone Place specializes in the sales and repair of phone accessories.

Visit dixonphone.com

Key Findings

We analyzed Dixonphone.com page load time and found that the first response time was 116 ms and then it took 2.5 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

dixonphone.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value1.095

1/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

dixonphone.com

116 ms

dixonphone.com

1425 ms

style.css

15 ms

style.css

29 ms

jquery.min.js

37 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 25% of them (13 requests) were addressed to the original Dixonphone.com, 34% (18 requests) were made to Fonts.gstatic.com and 26% (14 requests) were made to Sites.ipagepro.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dixonphone.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.1 kB (25%)

Content Size

628.4 kB

After Optimization

468.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dixonphone.com main page is 628.4 kB. 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. Images take 253.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 134.5 kB

  • Original 161.7 kB
  • After minification 158.6 kB
  • After compression 27.2 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 134.5 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 5.2 kB

  • Original 253.8 kB
  • After minification 248.6 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. Dixon Phone images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 19.8 kB

  • Original 210.1 kB
  • After minification 210.1 kB
  • After compression 190.4 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

-22%

Potential reduce by 590 B

  • Original 2.7 kB
  • After minification 2.7 kB
  • After compression 2.1 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. Dixonphone.com needs all CSS files to be minified and compressed as it can save up to 590 B or 22% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dixonphone.com

dixonphone.com

116 ms

dixonphone.com

dixonphone.com

1425 ms

style.css

style.css

15 ms

style.css

style.css

29 ms

jquery.min.js

jquery.min.js

37 ms

jquery-migrate.min.js

jquery-migrate.min.js

34 ms

email-decode.min.js

email-decode.min.js

12 ms

app.js

app.js

1 ms

scripts.min.js

scripts.min.js

27 ms

common.js

common.js

27 ms

sticky-elements.js

sticky-elements.js

54 ms

js

js

191 ms

Logo.png

Logo.png

172 ms

et-divi-dynamic-tb-695-tb-740-2-late.css

et-divi-dynamic-tb-695-tb-740-2-late.css

11 ms

hp-poly-logo.jpg

hp-poly-logo.jpg

140 ms

Header_right_img.png

Header_right_img.png

189 ms

homebanner.jpg

homebanner.jpg

444 ms

JabraLOGO.jpg

JabraLOGO.jpg

190 ms

Map.png

Map.png

191 ms

blue-seal-153-100-dixonphoneplace-8000634.png

blue-seal-153-100-dixonphoneplace-8000634.png

201 ms

Bing.png

Bing.png

192 ms

Googleplus.webp

Googleplus.webp

202 ms

Yahoo.png

Yahoo.png

202 ms

Visa.webp

Visa.webp

201 ms

MasterCard.webp

MasterCard.webp

202 ms

AMEX.webp

AMEX.webp

216 ms

Discover.webp

Discover.webp

228 ms

statistics.asp

statistics.asp

309 ms

track.js

track.js

312 ms

analytics.js

analytics.js

77 ms

Home_banner-1.jpg

Home_banner-1.jpg

127 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff

89 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf

100 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrc.woff

106 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrc.woff

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf

114 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrc.woff

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrc.woff

113 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf

128 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrc.woff

128 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf

126 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff

128 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf

128 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrc.woff

128 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf

129 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrc.woff

130 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf

128 ms

modules.woff

modules.woff

66 ms

collect

collect

28 ms

track-visibility.aspx

track-visibility.aspx

297 ms

push

push

269 ms

Accessibility Review

dixonphone.com accessibility score

68

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

dixonphone.com SEO score

99

Search Engine Optimization Advices

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

dixonphone.com

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