Tools & Wizards About Us
chasing.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

chasing.com

CHASING | The World's Most Innovative Underwater Drones

Page Load Speed

12.1 sec in total

First Response

227 ms

Resources Loaded

10.6 sec

Page Rendered

1.3 sec

chasing.com screenshot

About Website

Visit chasing.com now to see the best up-to-date CHASING content for United States and also check out these interesting facts you probably never knew about chasing.com

Explore the unexplored with CHASING Underwater Drones. Start shopping for consumer-grade or light-industrial-grade underwater ROVs with cameras.

Visit chasing.com

Key Findings

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

Performance Metrics

chasing.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value33.0 s

0/100

25%

SI (Speed Index)

Value38.7 s

0/100

10%

TBT (Total Blocking Time)

Value22,470 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value34.1 s

0/100

10%

Network Requests Diagram

chasing.com

227 ms

chasing.com

269 ms

819 ms

gtm.js

73 ms

idd1tqbpp5

64 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Chasing.com, 85% (101 requests) were made to Na-file.chasing.com and 2% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Na-file.chasing.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.3 MB (62%)

Content Size

11.7 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chasing.com main page is 11.7 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. 75% 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. HTML takes 7.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 6.9 MB

  • Original 7.8 MB
  • After minification 7.8 MB
  • After compression 886.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 6.9 MB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 794 B

  • Original 1.4 MB
  • After minification 1.4 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. CHASING images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 439.5 kB

  • Original 2.6 MB
  • After minification 2.6 MB
  • After compression 2.1 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 439.5 kB or 17% of the original size.

CSS Optimization

-0%

Potential reduce by 15 B

  • Original 4.7 kB
  • After minification 4.7 kB
  • After compression 4.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. Chasing.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 85 (79%)

Requests Now

108

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chasing.com

chasing.com

227 ms

chasing.com

chasing.com

269 ms

819 ms

gtm.js

gtm.js

73 ms

idd1tqbpp5

idd1tqbpp5

64 ms

css2

css2

40 ms

css

css

56 ms

aliplayer-min.css

aliplayer-min.css

145 ms

static.chasing-innovation.com_jquery-1.9.1.min.js

static.chasing-innovation.com_jquery-1.9.1.min.js

191 ms

flexible2.js

flexible2.js

3528 ms

aliplayer-h5-min.js

aliplayer-h5-min.js

268 ms

clarity.js

clarity.js

29 ms

runtime.815a9d1.js

runtime.815a9d1.js

1282 ms

header-block-drones.01e7b97c.7d48b7c.js

header-block-drones.01e7b97c.7d48b7c.js

1721 ms

header-block-explore.7a3f8cbd.73d813a.js

header-block-explore.7a3f8cbd.73d813a.js

2210 ms

header-block-user.8bfeee9b.defe20c.js

header-block-user.8bfeee9b.defe20c.js

2132 ms

header-block-lang.27770be6.9691db2.js

header-block-lang.27770be6.9691db2.js

2209 ms

header-block-car.74e494b9.06e1c96.js

header-block-car.74e494b9.06e1c96.js

2144 ms

c-button.0032492b.36953c5.js

c-button.0032492b.36953c5.js

2221 ms

index.31ecd969.2c6f80b.js

index.31ecd969.2c6f80b.js

1944 ms

index-banner.fa75b4c8.2a1f40c.js

index-banner.fa75b4c8.2a1f40c.js

2154 ms

c-banner.f2c2842d.324816b.js

c-banner.f2c2842d.324816b.js

2443 ms

c-video-item.f075b844.ae6ed7b.js

c-video-item.f075b844.ae6ed7b.js

2422 ms

index-honor.b6b4e5bf.86c9055.js

index-honor.b6b4e5bf.86c9055.js

2443 ms

index-rov.f3c88d6a.c327ee0.js

index-rov.f3c88d6a.c327ee0.js

2558 ms

c-svg-icon-link.17feffb3.c4ae683.js

c-svg-icon-link.17feffb3.c4ae683.js

2420 ms

index-application.ab331991.1860470.js

index-application.ab331991.1860470.js

2568 ms

index-read.01e7b97c.c5a7c47.js

index-read.01e7b97c.c5a7c47.js

2766 ms

index-media.01e7b97c.2f4b111.js

index-media.01e7b97c.2f4b111.js

2710 ms

index-new.4225ab6c.0369b94.js

index-new.4225ab6c.0369b94.js

2744 ms

c-new-item.01e7b97c.64c3c03.js

c-new-item.01e7b97c.64c3c03.js

2736 ms

index-shot.01e7b97c.59acf7f.js

index-shot.01e7b97c.59acf7f.js

2879 ms

index-shot-swiper.861a5e72.892ee2c.js

index-shot-swiper.861a5e72.892ee2c.js

2891 ms

index-story.01e7b97c.7ff55ab.js

index-story.01e7b97c.7ff55ab.js

2997 ms

index-dealer.01e7b97c.5dba024.js

index-dealer.01e7b97c.5dba024.js

3025 ms

vendors-element-ui.59f3426a.26955fa.js

vendors-element-ui.59f3426a.26955fa.js

2988 ms

vendors-element-ui.6ac3a2ba.63dee5f.js

vendors-element-ui.6ac3a2ba.63dee5f.js

3598 ms

vendors-element-ui.9ad0f35b.bdcdfaf.js

vendors-element-ui.9ad0f35b.bdcdfaf.js

3595 ms

vendors-element-ui.fe785c75.0b131c8.js

vendors-element-ui.fe785c75.0b131c8.js

3595 ms

vendors-element-ui.937f2c5e.983dad1.js

vendors-element-ui.937f2c5e.983dad1.js

3598 ms

vendors-element-ui.6ffbf29f.d6f364b.js

vendors-element-ui.6ffbf29f.d6f364b.js

3595 ms

app.f69643ec.3a0e643.js

app.f69643ec.3a0e643.js

3596 ms

app.8c7c996f.6cd6ae5.js

app.8c7c996f.6cd6ae5.js

3600 ms

app.a8d30b49.e790c2c.js

app.a8d30b49.e790c2c.js

3600 ms

app.8a386bb4.e2c617c.js

app.8a386bb4.e2c617c.js

3598 ms

app.6e16c056.752396b.js

app.6e16c056.752396b.js

3600 ms

app.a8a99674.463e07e.js

app.a8a99674.463e07e.js

3600 ms

app.c9a0212d.99696ca.js

app.c9a0212d.99696ca.js

3699 ms

app.6e48c680.2d1c889.js

app.6e48c680.2d1c889.js

2461 ms

app.0b94f024.333a596.js

app.0b94f024.333a596.js

2031 ms

app.0d834253.6033095.js

app.0d834253.6033095.js

1858 ms

app.9cbdb01a.6bf0c9a.js

app.9cbdb01a.6bf0c9a.js

1706 ms

app.77d82798.dd460bd.js

app.77d82798.dd460bd.js

1728 ms

app.ab6a7c49.d7c78ea.js

app.ab6a7c49.d7c78ea.js

1777 ms

app.69d8731c.805e3fc.js

app.69d8731c.805e3fc.js

1810 ms

app.c2b4f9a2.c0423da.js

app.c2b4f9a2.c0423da.js

1813 ms

app.0fb80869.623404b.js

app.0fb80869.623404b.js

1857 ms

app.7507fa27.8985506.js

app.7507fa27.8985506.js

1691 ms

app.42832916.e3f4e51.js

app.42832916.e3f4e51.js

1691 ms

app.1a57792e.478eec7.js

app.1a57792e.478eec7.js

1739 ms

app.4496087d.91ecf50.js

app.4496087d.91ecf50.js

1863 ms

app.94505caf.7419f3c.js

app.94505caf.7419f3c.js

1755 ms

app.382a2b0a.57ede0d.js

app.382a2b0a.57ede0d.js

1799 ms

app.1a998433.5145b6f.js

app.1a998433.5145b6f.js

1691 ms

app.de0ffa4a.f6df5e1.js

app.de0ffa4a.f6df5e1.js

1670 ms

app.2a8e0bc3.6bcb570.js

app.2a8e0bc3.6bcb570.js

1651 ms

app.bbe5006f.23a395f.js

app.bbe5006f.23a395f.js

1820 ms

app.7e96221d.8467e6e.js

app.7e96221d.8467e6e.js

1784 ms

app.d492abd4.f130758.js

app.d492abd4.f130758.js

1815 ms

app.d0ae3f07.5db5b8f.js

app.d0ae3f07.5db5b8f.js

1639 ms

app.62ab6885.566dc1c.js

app.62ab6885.566dc1c.js

1650 ms

app.fc2f81ef.6275560.js

app.fc2f81ef.6275560.js

1622 ms

ll1q8F7StzWuV5Ug72V9l9c7m6T6

ll1q8F7StzWuV5Ug72V9l9c7m6T6

109 ms

lqk2M4if3-Wrgfl2EDDx_VlNPA38

lqk2M4if3-Wrgfl2EDDx_VlNPA38

730 ms

app.fab76d83.f72a150.js

app.fab76d83.f72a150.js

1243 ms

app.b5906859.6ee4d5f.js

app.b5906859.6ee4d5f.js

1253 ms

app.70aabc29.b01b64c.js

app.70aabc29.b01b64c.js

1274 ms

app.f9ca8911.2747bfb.js

app.f9ca8911.2747bfb.js

1300 ms

app.b5ca00bf.ed0ec7b.js

app.b5ca00bf.ed0ec7b.js

1353 ms

app.cfbf0a2e.8b285eb.js

app.cfbf0a2e.8b285eb.js

1339 ms

app.fdc6512a.2a8fa40.js

app.fdc6512a.2a8fa40.js

1461 ms

app.8546d4a7.5805097.js

app.8546d4a7.5805097.js

1481 ms

app.3b3d3141.58b253a.js

app.3b3d3141.58b253a.js

1536 ms

app.5da307cb.1b5c4fa.js

app.5da307cb.1b5c4fa.js

1555 ms

font

font

64 ms

app.e48ca888.9dad9ca.js

app.e48ca888.9dad9ca.js

1568 ms

sdk.js

sdk.js

95 ms

sdk.js

sdk.js

7 ms

app.060b3b31.29b5a91.js

app.060b3b31.29b5a91.js

1463 ms

app.a22590d6.ecd65ff.js

app.a22590d6.ecd65ff.js

1654 ms

app.6ff199a4.e8919ec.js

app.6ff199a4.e8919ec.js

1567 ms

app.0605657e.5336739.js

app.0605657e.5336739.js

1608 ms

app.aaac3122.734e31b.js

app.aaac3122.734e31b.js

1614 ms

app.4c0201b9.f65cfae.js

app.4c0201b9.f65cfae.js

1527 ms

app.95a964c1.ca2b282.js

app.95a964c1.ca2b282.js

1476 ms

-WEBP

-WEBP

1741 ms

na-file.chasing.com

na-file.chasing.com

1808 ms

newindex_img1.1a1a4f7.jpg

newindex_img1.1a1a4f7.jpg

2736 ms

newindex_img2.2b39444.jpg

newindex_img2.2b39444.jpg

2264 ms

newindex_img3.dae5b0b.jpg

newindex_img3.dae5b0b.jpg

2549 ms

newindex_img5.d8809d4.png

newindex_img5.d8809d4.png

1730 ms

newindex_img6.63f1e0d.png

newindex_img6.63f1e0d.png

1947 ms

newindex_img7.88e594d.png

newindex_img7.88e594d.png

2001 ms

newindex_img8.cbb64e2.png

newindex_img8.cbb64e2.png

2257 ms

newindex_img9.25c4a0e.png

newindex_img9.25c4a0e.png

2624 ms

newindex_img10.f3c8f8c.png

newindex_img10.f3c8f8c.png

2631 ms

newindex_img11.c458faa.png

newindex_img11.c458faa.png

2407 ms

newindex_img12.1ac61ff.png

newindex_img12.1ac61ff.png

2541 ms

newindex_img17.a5e33b2.png

newindex_img17.a5e33b2.png

2495 ms

newindex_img18.04c06b3.png

newindex_img18.04c06b3.png

2611 ms

newindex_img19.5bcefaa.jpg

newindex_img19.5bcefaa.jpg

3138 ms

newindex_img20.5900bc5.jpg

newindex_img20.5900bc5.jpg

3265 ms

na-file.chasing.com

na-file.chasing.com

1429 ms

na-file.chasing.com

na-file.chasing.com

219 ms

na-file.chasing.com

na-file.chasing.com

220 ms

na-file.chasing.com

na-file.chasing.com

221 ms

na-file.chasing.com

na-file.chasing.com

221 ms

na-file.chasing.com

na-file.chasing.com

224 ms

c.gif

c.gif

7 ms

Accessibility Review

chasing.com accessibility score

74

Accessibility Issues

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

Image elements do not have [alt] attributes

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

chasing.com best practices score

58

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

SEO Factors

chasing.com SEO score

85

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

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

chasing.com

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