Tools & Wizards About Us
phoenixmechanicshop.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

phoenixmechanicshop.com

Transmission & Automotive Repair | Phoenix | Advanced Transmissions & Emissions

Page Load Speed

7 sec in total

First Response

260 ms

Resources Loaded

5.5 sec

Page Rendered

1.2 sec

phoenixmechanicshop.com screenshot

About Website

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

We expertly repair transmissions, clutches, AC, suspension, & more. Contact us for your Phoenix transmission & automotive repair needs.

Visit phoenixmechanicshop.com

Key Findings

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

Performance Metrics

phoenixmechanicshop.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value24.0 s

0/100

10%

TBT (Total Blocking Time)

Value47,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.325

35/100

15%

TTI (Time to Interactive)

Value62.0 s

0/100

10%

Network Requests Diagram

www.phoenixtransmissionshop.com

260 ms

www.phoenixtransmissionshop.com

498 ms

wp-emoji-release.min.js

290 ms

style.min.css

207 ms

all.min.css

147 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Phoenixmechanicshop.com, 13% (11 requests) were made to Youtube.com and 5% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Js.calltrk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 423.2 kB (30%)

Content Size

1.4 MB

After Optimization

979.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoenixmechanicshop.com main page is 1.4 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. 80% 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 814.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 86.3 kB

  • Original 108.2 kB
  • After minification 106.5 kB
  • After compression 21.9 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 86.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 814.7 kB
  • After minification 814.7 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. Phoenix Mechanicshop images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 25.3 kB

  • Original 111.4 kB
  • After minification 111.4 kB
  • After compression 86.2 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 25.3 kB or 23% of the original size.

CSS Optimization

-85%

Potential reduce by 311.7 kB

  • Original 368.8 kB
  • After minification 368.6 kB
  • After compression 57.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. Phoenixmechanicshop.com needs all CSS files to be minified and compressed as it can save up to 311.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (69%)

Requests Now

75

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.phoenixtransmissionshop.com

www.phoenixtransmissionshop.com

260 ms

www.phoenixtransmissionshop.com

www.phoenixtransmissionshop.com

498 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

290 ms

style.min.css

style.min.css

207 ms

all.min.css

all.min.css

147 ms

foundation-icons.css

foundation-icons.css

96 ms

5-layout.css

5-layout.css

201 ms

widget-areas.min.css

widget-areas.min.css

411 ms

main.min.css

main.min.css

314 ms

featured-images.min.css

featured-images.min.css

184 ms

offside.min.css

offside.min.css

216 ms

navigation-branding-flex.min.css

navigation-branding-flex.min.css

278 ms

jquery.min.js

jquery.min.js

239 ms

jquery-migrate.min.js

jquery-migrate.min.js

240 ms

f7c86a02b15ec7ebe03bdbbe7f3fbf2a1e3650fde32f7180

f7c86a02b15ec7ebe03bdbbe7f3fbf2a1e3650fde32f7180

332 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

278 ms

wp-polyfill.min.js

wp-polyfill.min.js

283 ms

dom-ready.min.js

dom-ready.min.js

728 ms

hooks.min.js

hooks.min.js

306 ms

i18n.min.js

i18n.min.js

326 ms

a11y.min.js

a11y.min.js

336 ms

jquery.json.min.js

jquery.json.min.js

346 ms

gravityforms.min.js

gravityforms.min.js

345 ms

api.js

api.js

113 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

346 ms

sticky.min.js

sticky.min.js

353 ms

offside.min.js

offside.min.js

372 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

827 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

377 ms

5-layout.js

5-layout.js

434 ms

smooth-scroll.min.js

smooth-scroll.min.js

528 ms

menu.min.js

menu.min.js

530 ms

1143664-Clear-Background_080421-1-1024x458.png

1143664-Clear-Background_080421-1-1024x458.png

393 ms

1143664-Clear-Background_080421.png

1143664-Clear-Background_080421.png

117 ms

1143664-Clear-Background_080421-1.png

1143664-Clear-Background_080421-1.png

860 ms

icon1.svg

icon1.svg

100 ms

icon2.svg

icon2.svg

392 ms

icon3.svg

icon3.svg

288 ms

icon4.svg

icon4.svg

285 ms

icon5.svg

icon5.svg

394 ms

gtm.js

gtm.js

399 ms

maqEFjgZlko

maqEFjgZlko

324 ms

AdvancedTransmissionsAndEmissions-500577714.jpg

AdvancedTransmissionsAndEmissions-500577714.jpg

300 ms

AdvancedTransmissionsAndEmissions-1001604846.jpg

AdvancedTransmissionsAndEmissions-1001604846.jpg

299 ms

fa-solid-900.woff

fa-solid-900.woff

571 ms

fa-regular-400.woff

fa-regular-400.woff

569 ms

foundation-icons.woff

foundation-icons.woff

90 ms

www-player.css

www-player.css

313 ms

www-embed-player.js

www-embed-player.js

313 ms

base.js

base.js

312 ms

fetch-polyfill.js

fetch-polyfill.js

312 ms

recaptcha__en.js

recaptcha__en.js

685 ms

ISS_23421_00229-scaled.jpg

ISS_23421_00229-scaled.jpg

332 ms

maqEFjgZlko

maqEFjgZlko

272 ms

conversion_async.js

conversion_async.js

332 ms

b5aa727d-295c-4ad8-adb8-44944b60896e.js

b5aa727d-295c-4ad8-adb8-44944b60896e.js

324 ms

bat.js

bat.js

321 ms

swap.js

swap.js

320 ms

www-player.css

www-player.css

59 ms

www-embed-player.js

www-embed-player.js

163 ms

base.js

base.js

276 ms

fetch-polyfill.js

fetch-polyfill.js

157 ms

760 ms

external_forms.js

external_forms.js

840 ms

swap_session.json

swap_session.json

1019 ms

js

js

577 ms

ad_status.js

ad_status.js

650 ms

25151412.js

25151412.js

477 ms

qs_eGd-h9f3_frMeplByuCjrJjGTr5iyl3j-JE2Mo0s.js

qs_eGd-h9f3_frMeplByuCjrJjGTr5iyl3j-JE2Mo0s.js

236 ms

embed.js

embed.js

134 ms

js

js

200 ms

analytics.js

analytics.js

437 ms

fbevents.js

fbevents.js

407 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

384 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

374 ms

25151412

25151412

430 ms

112 ms

id

id

247 ms

icap.js

icap.js

124 ms

1240328679764204

1240328679764204

96 ms

Create

Create

449 ms

collect

collect

327 ms

collect

collect

320 ms

collect

collect

213 ms

clarity.js

clarity.js

57 ms

ga-audiences

ga-audiences

36 ms

c.gif

c.gif

65 ms

Accessibility Review

phoenixmechanicshop.com accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

phoenixmechanicshop.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

phoenixmechanicshop.com SEO score

100

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

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

phoenixmechanicshop.com

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