Tools & Wizards About Us
findlayhonda.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% 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

  • 84

    SEO

    Google-friendlier than
    52% of websites

findlayhonda.com

Findlay Honda in Centennial Hills | Las Vegas Honda Dealer

Page Load Speed

22.2 sec in total

First Response

158 ms

Resources Loaded

21.9 sec

Page Rendered

187 ms

findlayhonda.com screenshot

About Website

Click here to check amazing Findlay Honda content for United States. Otherwise, check out these important facts you probably never knew about findlayhonda.com

Finance a new Honda or used car at our Las Vegas Honda dealership. Visit Findlay Honda in Centennial Hills for auto service or to start a new Honda lease.

Visit findlayhonda.com

Key Findings

We analyzed Findlayhonda.com page load time and found that the first response time was 158 ms and then it took 22 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

findlayhonda.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value35.9 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value14,730 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value44.4 s

0/100

10%

Network Requests Diagram

findlayhonda.com

158 ms

fbevents.js

104 ms

bat.js

156 ms

js

159 ms

gtm.js

275 ms

Our browser made a total of 144 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Findlayhonda.com, 26% (37 requests) were made to S.amazon-adsystem.com and 15% (21 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Public-prod-dspcookiematching.dmxleo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.0 kB (18%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Findlayhonda.com main page is 1.5 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. Only a small number of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 248.0 kB

  • Original 300.0 kB
  • After minification 281.2 kB
  • After compression 52.0 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 248.0 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 5 B

  • Original 344 B
  • After minification 339 B

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. Findlay Honda images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 24.9 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 1.2 MB

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 44 B

  • Original 16.6 kB
  • After minification 16.6 kB
  • After compression 16.5 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. Findlayhonda.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

115

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

findlayhonda.com

findlayhonda.com

158 ms

fbevents.js

fbevents.js

104 ms

bat.js

bat.js

156 ms

js

js

159 ms

gtm.js

gtm.js

275 ms

gtm.js

gtm.js

285 ms

gtm.js

gtm.js

285 ms

gtm.js

gtm.js

213 ms

20379.js

20379.js

214 ms

t.js

t.js

158 ms

up.js

up.js

212 ms

tms.js

tms.js

527 ms

blocker.js

blocker.js

272 ms

vendor.css

vendor.css

307 ms

js

js

304 ms

js

js

306 ms

jquery.min.js

jquery.min.js

154 ms

snap-xoRgY7ebzuKot4nCB.js

snap-xoRgY7ebzuKot4nCB.js

333 ms

common.js

common.js

332 ms

vendor.js

vendor.js

364 ms

conversion.js

conversion.js

302 ms

loader.js

loader.js

266 ms

loader_102870_3.js

loader_102870_3.js

302 ms

banner.js

banner.js

331 ms

landing.css

landing.css

329 ms

landing.main.js

landing.main.js

710 ms

js

js

363 ms

analytics.js

analytics.js

509 ms

js

js

267 ms

destination

destination

262 ms

stat.js

stat.js

445 ms

gtm.js

gtm.js

439 ms

gtm.js

gtm.js

440 ms

js

js

391 ms

js

js

390 ms

GetLibraryImage

GetLibraryImage

562 ms

GetLibraryImage

GetLibraryImage

564 ms

snap-xoRgY7ebzuKot4nCB.js

snap-xoRgY7ebzuKot4nCB.js

711 ms

gtm.latest.js

gtm.latest.js

579 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

549 ms

fullthrottlelims.js

fullthrottlelims.js

579 ms

9981715add36807e4c747ac640138054.woff

9981715add36807e4c747ac640138054.woff

290 ms

tp2

tp2

182 ms

collect

collect

132 ms

collect

collect

133 ms

atmain2.js

atmain2.js

78 ms

iu3

iu3

39 ms

collect

collect

12 ms

js

js

56 ms

ga-audiences

ga-audiences

538 ms

pr

pr

38 ms

generic

generic

102 ms

687 ms

setuid

setuid

683 ms

Serving

Serving

792 ms

amazon

amazon

682 ms

dspreply

dspreply

19699 ms

map

map

930 ms

usermatch.gif

usermatch.gif

69 ms

v1

v1

740 ms

pixel

pixel

785 ms

v2

v2

67 ms

usersync

usersync

832 ms

ecm3

ecm3

910 ms

ecm3

ecm3

408 ms

collect

collect

404 ms

collect

collect

578 ms

collect

collect

641 ms

386 ms

clarivoy.js

clarivoy.js

381 ms

partnermetrics.js

partnermetrics.js

807 ms

gtm.js

gtm.js

449 ms

styles.css

styles.css

360 ms

gtm.js

gtm.js

494 ms

eas.js

eas.js

773 ms

gtm.js

gtm.js

363 ms

collect

collect

287 ms

js

js

335 ms

styles.css

styles.css

279 ms

641 ms

ecm3

ecm3

254 ms

ecm3

ecm3

353 ms

collect

collect

238 ms

js

js

252 ms

ecm3

ecm3

471 ms

ecm3

ecm3

458 ms

ecm3

ecm3

410 ms

ecm3

ecm3

407 ms

tms.js

tms.js

406 ms

ecm3

ecm3

406 ms

ecm3

ecm3

421 ms

collect

collect

265 ms

js

js

263 ms

ecm3

ecm3

419 ms

pixel

pixel

369 ms

ecm3

ecm3

386 ms

ga-audiences

ga-audiences

362 ms

ecm3

ecm3

380 ms

ecm3

ecm3

378 ms

ecm3

ecm3

377 ms

ecm3

ecm3

389 ms

ecm3

ecm3

390 ms

rubicon

rubicon

221 ms

2245d8ca6bbe51e06aa5a4a6d353bf51.woff

2245d8ca6bbe51e06aa5a4a6d353bf51.woff

302 ms

0a36c90fc39ef551885b4a4e6f1c4193.woff

0a36c90fc39ef551885b4a4e6f1c4193.woff

302 ms

ecm3

ecm3

266 ms

ecm3

ecm3

265 ms

ecm3

ecm3

263 ms

ecm3

ecm3

250 ms

ecm3

ecm3

256 ms

ecm3

ecm3

257 ms

ecm3

ecm3

253 ms

recordMetricsData.action

recordMetricsData.action

271 ms

pixel

pixel

157 ms

ecm3

ecm3

175 ms

ecm3

ecm3

177 ms

ecm3

ecm3

51 ms

ecm3

ecm3

56 ms

ecm3

ecm3

55 ms

ecm3

ecm3

64 ms

ecm3

ecm3

56 ms

ecm3

ecm3

54 ms

ecm3

ecm3

46 ms

edw_partner.cgi

edw_partner.cgi

19539 ms

google

google

19 ms

24 ms

segment

segment

31 ms

segment

segment

30 ms

ecm3

ecm3

15 ms

generic

generic

7 ms

receive

receive

20 ms

appnexus

appnexus

5 ms

ecm3

ecm3

9 ms

pixel

pixel

20 ms

ecm3

ecm3

10 ms

114 ms

jdp_208451-dx-scr.js

jdp_208451-dx-scr.js

44 ms

48 ms

6 ms

syncd

syncd

4 ms

4 ms

receive

receive

21 ms

49 ms

46 ms

Accessibility Review

findlayhonda.com accessibility score

96

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-hidden="true"] elements contain focusable descendents

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.

Best Practices

findlayhonda.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

findlayhonda.com SEO score

84

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

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

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

findlayhonda.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: