Tools & Wizards About Us
cokertire.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

cokertire.com

Home | Coker Tire

Page Load Speed

4.2 sec in total

First Response

649 ms

Resources Loaded

3.1 sec

Page Rendered

447 ms

cokertire.com screenshot

About Website

Welcome to cokertire.com homepage info - get ready to check Coker Tire best content for United States right away, or after learning these important things about cokertire.com

Coker Tire

Visit cokertire.com

Key Findings

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

cokertire.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value2,820 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.197

63/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

www.cokertire.com

649 ms

custom.css

60 ms

styles.css

80 ms

searchautocomplete.css

80 ms

searchautocomplete_custom.css

83 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 68% of them (102 requests) were addressed to the original Cokertire.com, 5% (7 requests) were made to Apis.google.com and 5% (7 requests) were made to Server.iad.liveperson.net. The less responsive or slowest element that took the longest time to load (649 ms) belongs to the original domain Cokertire.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (34%)

Content Size

3.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cokertire.com main page is 3.2 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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 173.1 kB

  • Original 205.8 kB
  • After minification 180.8 kB
  • After compression 32.6 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. This page needs HTML code to be minified as it can gain 25.0 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 173.1 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 26.3 kB

  • Original 1.8 MB
  • After minification 1.8 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. Coker Tire images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 725.2 kB

  • Original 990.0 kB
  • After minification 793.0 kB
  • After compression 264.8 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 725.2 kB or 73% of the original size.

CSS Optimization

-81%

Potential reduce by 143.1 kB

  • Original 177.8 kB
  • After minification 170.2 kB
  • After compression 34.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. Cokertire.com needs all CSS files to be minified and compressed as it can save up to 143.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (67%)

Requests Now

141

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.cokertire.com

www.cokertire.com

649 ms

custom.css

custom.css

60 ms

styles.css

styles.css

80 ms

searchautocomplete.css

searchautocomplete.css

80 ms

searchautocomplete_custom.css

searchautocomplete_custom.css

83 ms

recentlyviewed.css

recentlyviewed.css

84 ms

ajaxlayerednavigation.css

ajaxlayerednavigation.css

81 ms

ion.rangeSlider.css

ion.rangeSlider.css

88 ms

ion.rangeSlider.skinNice.css

ion.rangeSlider.skinNice.css

82 ms

prototype.js

prototype.js

115 ms

ccard.js

ccard.js

98 ms

validation.js

validation.js

135 ms

builder.js

builder.js

103 ms

effects.js

effects.js

108 ms

dragdrop.js

dragdrop.js

132 ms

controls.js

controls.js

138 ms

slider.js

slider.js

141 ms

js.js

js.js

145 ms

form.js

form.js

147 ms

menu.js

menu.js

149 ms

translate.js

translate.js

145 ms

cookies.js

cookies.js

148 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

181 ms

jquery-noConflict.js

jquery-noConflict.js

149 ms

modernizr.js

modernizr.js

159 ms

ajaxcartpro.js

ajaxcartpro.js

157 ms

cart.js

cart.js

156 ms

sidebar.js

sidebar.js

154 ms

topLinks.js

topLinks.js

162 ms

skipLinks.js

skipLinks.js

173 ms

options.js

options.js

175 ms

wishlist.js

wishlist.js

203 ms

miniWishlist.js

miniWishlist.js

176 ms

addProductConfirmation.js

addProductConfirmation.js

203 ms

removeProductConfirmation.js

removeProductConfirmation.js

204 ms

clickOnButtonInCartPageForm.js

clickOnButtonInCartPageForm.js

205 ms

ara8ite.js

ara8ite.js

208 ms

platform.js

platform.js

136 ms

conversion.js

conversion.js

64 ms

clickOnAddToCartInCategoryList.js

clickOnAddToCartInCategoryList.js

201 ms

clickOnAddToCartInOptionsPopup.js

clickOnAddToCartInOptionsPopup.js

145 ms

clickOnAddToCartInProductPage.js

clickOnAddToCartInProductPage.js

141 ms

clickOnDeleteFromCart.js

clickOnDeleteFromCart.js

141 ms

clickOnAddToCartInMiniWishlist.js

clickOnAddToCartInMiniWishlist.js

146 ms

product.js

product.js

157 ms

product.js

product.js

148 ms

main.js

main.js

150 ms

faq.js

faq.js

148 ms

bundle.js

bundle.js

142 ms

recentlyviewed.js

recentlyviewed.js

141 ms

ajaxlayerednavigation.js

ajaxlayerednavigation.js

119 ms

ion.rangeSlider.js

ion.rangeSlider.js

118 ms

offcanvas.js

offcanvas.js

116 ms

jquery-ui.min.js

jquery-ui.min.js

133 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

131 ms

jquery.easing.min.js

jquery.easing.min.js

129 ms

scotchPanels.min.js

scotchPanels.min.js

128 ms

common.js

common.js

127 ms

bootstrap.min.js

bootstrap.min.js

127 ms

jquery.finger.min.js

jquery.finger.min.js

128 ms

svg.js

svg.js

130 ms

search_site.js

search_site.js

152 ms

gaevents.js

gaevents.js

151 ms

login.js

login.js

148 ms

myaccount.js

myaccount.js

147 ms

analytics.js

analytics.js

58 ms

www.cokertire.com

www.cokertire.com

28 ms

fbds.js

fbds.js

499 ms

loader.js

loader.js

80 ms

cart.svg

cart.svg

44 ms

CokerTire_logo.png

CokerTire_logo.png

43 ms

Coker-Classic-Rebate-hp.jpg

Coker-Classic-Rebate-hp.jpg

81 ms

CTC-American-Classic-slider-revised.jpg

CTC-American-Classic-slider-revised.jpg

321 ms

Wooden_Wheels.jpg

Wooden_Wheels.jpg

48 ms

Coker_whitewalls.jpg

Coker_whitewalls.jpg

125 ms

tires.png

tires.png

63 ms

wheels_1.png

wheels_1.png

81 ms

tube.png

tube.png

79 ms

accessories.png

accessories.png

80 ms

apparel.png

apparel.png

97 ms

collectables.png

collectables.png

96 ms

Military_400X317.jpg

Military_400X317.jpg

97 ms

Silvertown_400X317.jpg

Silvertown_400X317.jpg

138 ms

Firestone_400X317.jpg

Firestone_400X317.jpg

126 ms

facebook.svg

facebook.svg

125 ms

youtube.svg

youtube.svg

123 ms

instagram.svg

instagram.svg

140 ms

twitter.svg

twitter.svg

136 ms

coker_main.png

coker_main.png

138 ms

gr_logo.png

gr_logo.png

151 ms

coker_cycles_logo.png

coker_cycles_logo.png

266 ms

hc_logo.png

hc_logo.png

270 ms

ajax-loader_1.gif

ajax-loader_1.gif

267 ms

magnify.svg

magnify.svg

255 ms

collect

collect

39 ms

tag.js

tag.js

79 ms

fancy_arrow.svg

fancy_arrow.svg

211 ms

fancy_arrow_brown.svg

fancy_arrow_brown.svg

215 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

216 ms

collect

collect

198 ms

9hHpx0O4t9O6XNKKwM_6pnCBdid2r9ze1bMszuFD949ffJn6ggMdeMJ6Mk6f5Mb.woff

9hHpx0O4t9O6XNKKwM_6pnCBdid2r9ze1bMszuFD949ffJn6ggMdeMJ6Mk6f5Mb.woff

202 ms

impl-1_22.js

impl-1_22.js

30 ms

seo_pre_footer.jpg

seo_pre_footer.jpg

343 ms

round_arrow.svg

round_arrow.svg

184 ms

arrow_right.svg

arrow_right.svg

183 ms

sdk.js

sdk.js

586 ms

widgets.js

widgets.js

255 ms

arrow_right_yellow.svg

arrow_right_yellow.svg

206 ms

horizontal_divider.gif

horizontal_divider.gif

208 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

193 ms

.jsonp

.jsonp

286 ms

140 ms

cart.svg

cart.svg

153 ms

facebook.svg

facebook.svg

166 ms

youtube.svg

youtube.svg

143 ms

instagram.svg

instagram.svg

158 ms

twitter.svg

twitter.svg

171 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

113 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

207 ms

fastbutton

fastbutton

228 ms

ga-audiences

ga-audiences

233 ms

p.gif

p.gif

283 ms

176 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

94 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

42 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

44 ms

mTag.js

mTag.js

162 ms

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf

105 ms

postmessageRelay

postmessageRelay

70 ms

386 ms

304 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

52 ms

api.js

api.js

555 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

114 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

97 ms

13 ms

25 ms

11 ms

corky_face.png

corky_face.png

24 ms

24 ms

jot

jot

103 ms

46 ms

31 ms

197 ms

xd_arbiter.php

xd_arbiter.php

429 ms

wcm

wcm

48 ms

share_button.php

share_button.php

174 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

487 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

550 ms

Accessibility Review

cokertire.com accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

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

Image elements do not have [alt] attributes

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

cokertire.com best practices score

50

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

Displays images with incorrect aspect ratio

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

cokertire.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

cokertire.com

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