Tools & Wizards About Us
chasingplaces.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

chasingplaces.com

Chasing Places Travel Guide

Page Load Speed

2.1 sec in total

First Response

195 ms

Resources Loaded

1.3 sec

Page Rendered

580 ms

chasingplaces.com screenshot

About Website

Click here to check amazing Chasing Places content for Malaysia. Otherwise, check out these important facts you probably never knew about chasingplaces.com

Your SMART travel guide website/blog, that features over 100 destinations in Asia and around the world. Helping you plan your trip and transport with ease.

Visit chasingplaces.com

Key Findings

We analyzed Chasingplaces.com page load time and found that the first response time was 195 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

chasingplaces.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value4,430 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.381

27/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

chasingplaces.com

195 ms

chasingplaces.com

402 ms

gtm-367f85a6c87a3404274d37533eb93b4a.js

31 ms

frontend-gtag.min.js

36 ms

front.min.js

55 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 92% of them (71 requests) were addressed to the original Chasingplaces.com, 3% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (643 ms) belongs to the original domain Chasingplaces.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.4 kB (23%)

Content Size

1.1 MB

After Optimization

874.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Chasingplaces.com main page is 1.1 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 742.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 256.1 kB

  • Original 323.6 kB
  • After minification 323.6 kB
  • After compression 67.5 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 256.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 293 B

  • Original 742.0 kB
  • After minification 741.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. Chasing Places images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 18 B

  • Original 65.4 kB
  • After minification 65.4 kB
  • After compression 65.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.

Requests Breakdown

Number of requests can be reduced by 56 (76%)

Requests Now

74

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chasingplaces.com

chasingplaces.com

195 ms

chasingplaces.com

chasingplaces.com

402 ms

gtm-367f85a6c87a3404274d37533eb93b4a.js

gtm-367f85a6c87a3404274d37533eb93b4a.js

31 ms

frontend-gtag.min.js

frontend-gtag.min.js

36 ms

front.min.js

front.min.js

55 ms

js

js

113 ms

js

js

254 ms

fbevents.js

fbevents.js

77 ms

adsbygoogle.js

adsbygoogle.js

228 ms

profile-3.jpg

profile-3.jpg

99 ms

cropped-retinalogo-225x159.png

cropped-retinalogo-225x159.png

36 ms

homepage2.jpg

homepage2.jpg

88 ms

feature.jpg

feature.jpg

55 ms

feature-2.jpg

feature-2.jpg

58 ms

Feature-2.jpg

Feature-2.jpg

56 ms

3-600x272.jpg

3-600x272.jpg

86 ms

kuala-lumpur.jpg

kuala-lumpur.jpg

58 ms

40-flights.jpg

40-flights.jpg

88 ms

lombok.jpg

lombok.jpg

89 ms

malta-sample2.jpg

malta-sample2.jpg

208 ms

discovercars-blue-400.png

discovercars-blue-400.png

88 ms

agoda.png

agoda.png

415 ms

bookingcom.png

bookingcom.png

643 ms

cheapoairedited.jpg

cheapoairedited.jpg

642 ms

bookingbuddyedited.png

bookingbuddyedited.png

642 ms

main.min.css

main.min.css

90 ms

css

css

89 ms

style-4e7fb8ab9515ee0f67d59b6d78ffdf70.css

style-4e7fb8ab9515ee0f67d59b6d78ffdf70.css

199 ms

public-c7356556d1a998ede3e6e51dcd83a61e.css

public-c7356556d1a998ede3e6e51dcd83a61e.css

197 ms

classic-8dd55794bb00dd2d95e82fd6e6f57be5.css

classic-8dd55794bb00dd2d95e82fd6e6f57be5.css

196 ms

subscribe-forms.min.css

subscribe-forms.min.css

202 ms

click-to-tweet.min.css

click-to-tweet.min.css

204 ms

easy-social-share-buttons.min-18c54d639ad5459e438e8c2ed83e6130.css

easy-social-share-buttons.min-18c54d639ad5459e438e8c2ed83e6130.css

208 ms

front.min.css

front.min.css

206 ms

b36bac7950684563c897f8466df0dc89.min-50b44ceaa9df2974c9d5928528fb5697.css

b36bac7950684563c897f8466df0dc89.min-50b44ceaa9df2974c9d5928528fb5697.css

231 ms

frontend.min.js

frontend.min.js

204 ms

jquery.min.js

jquery.min.js

211 ms

jquery-migrate.min.js

jquery-migrate.min.js

210 ms

modernizr-843d6cd2f596a1af3ec48baa8683f55b.js

modernizr-843d6cd2f596a1af3ec48baa8683f55b.js

211 ms

fusion-column-bg-image-a7679c30b9cc3e0b41598e977e915ab6.js

fusion-column-bg-image-a7679c30b9cc3e0b41598e977e915ab6.js

224 ms

cssua-8bda6d0f8ce6e53da52b2c359dcc5e54.js

cssua-8bda6d0f8ce6e53da52b2c359dcc5e54.js

224 ms

fusion-92a461d367721818903d6e5fb4eb99dd.js

fusion-92a461d367721818903d6e5fb4eb99dd.js

229 ms

isotope-e9964e2e0766e003f62d4fa40871b7c5.js

isotope-e9964e2e0766e003f62d4fa40871b7c5.js

225 ms

packery-154d80c9eaea02229d0de0ddaca4cba7.js

packery-154d80c9eaea02229d0de0ddaca4cba7.js

226 ms

bootstrap.tooltip-51431d51c14351e489dce76853861a3d.js

bootstrap.tooltip-51431d51c14351e489dce76853861a3d.js

226 ms

jquery.requestAnimationFrame-65605143336ed5ba8a02c1416060efea.js

jquery.requestAnimationFrame-65605143336ed5ba8a02c1416060efea.js

226 ms

jquery.easing-81d9f1dbd4ec7d66535fe84eab62396a.js

jquery.easing-81d9f1dbd4ec7d66535fe84eab62396a.js

254 ms

jquery.fitvids-5b88c33e00e8f8be2fce2a54b50e6f68.js

jquery.fitvids-5b88c33e00e8f8be2fce2a54b50e6f68.js

254 ms

jquery.flexslider-feaf3ea5b69479e0b52c57178dc4cf24.js

jquery.flexslider-feaf3ea5b69479e0b52c57178dc4cf24.js

249 ms

jquery.hoverflow-577618794d36e82462ce81daf97be079.js

jquery.hoverflow-577618794d36e82462ce81daf97be079.js

230 ms

jquery.ilightbox-c785dee727c4dafed7307e737dc04910.js

jquery.ilightbox-c785dee727c4dafed7307e737dc04910.js

230 ms

jquery.infinitescroll-61b199e7fd697e636f7bcae16876ad50.js

jquery.infinitescroll-61b199e7fd697e636f7bcae16876ad50.js

371 ms

jquery.mousewheel-32e0c3aeea34514673afd08a0fa33ab1.js

jquery.mousewheel-32e0c3aeea34514673afd08a0fa33ab1.js

211 ms

jquery.placeholder-3dab585bbeb5e4bc971a5094830d2ae0.js

jquery.placeholder-3dab585bbeb5e4bc971a5094830d2ae0.js

350 ms

jquery.fade-d799790e1d05a896d443c624f19d2694.js

jquery.fade-d799790e1d05a896d443c624f19d2694.js

346 ms

imagesLoaded-9cc964a30eff08e7f3de27aa0894cb1f.js

imagesLoaded-9cc964a30eff08e7f3de27aa0894cb1f.js

346 ms

fusion-equal-heights-d5c2550aa3949b1b3484bbcb83ccdf7e.js

fusion-equal-heights-d5c2550aa3949b1b3484bbcb83ccdf7e.js

317 ms

fusion-parallax-dc2ca5f4b80a6cb261bfaa298b953737.js

fusion-parallax-dc2ca5f4b80a6cb261bfaa298b953737.js

317 ms

fusion-video-general-459baf6ac3ccdad8e433ae0cb6d0a184.js

fusion-video-general-459baf6ac3ccdad8e433ae0cb6d0a184.js

317 ms

fusion-video-bg-e30c43304c472f6c8ea17ce33fdc1975.js

fusion-video-bg-e30c43304c472f6c8ea17ce33fdc1975.js

316 ms

fusion-lightbox-637c79699b3c694f5b530666b07ceddd.js

fusion-lightbox-637c79699b3c694f5b530666b07ceddd.js

317 ms

fusion-flexslider-860b98765ea3012de75e8ab827185e97.js

fusion-flexslider-860b98765ea3012de75e8ab827185e97.js

279 ms

fusion-tooltip-6593207cbccbc08fc99be457f06d5402.js

fusion-tooltip-6593207cbccbc08fc99be457f06d5402.js

205 ms

fusion-sharing-box-48c3d0c1ebb6f76ca3990f65d128b779.js

fusion-sharing-box-48c3d0c1ebb6f76ca3990f65d128b779.js

202 ms

jquery.sticky-kit-b0909b863d3f9272adfc2817c0f49e26.js

jquery.sticky-kit-b0909b863d3f9272adfc2817c0f49e26.js

202 ms

fusion-button-5dcf8af34c58f91cbc1aa60f327dbea4.js

fusion-button-5dcf8af34c58f91cbc1aa60f327dbea4.js

200 ms

fusion-blog-962f011e52b5b1bbf66f8f7a3a3fa2f9.js

fusion-blog-962f011e52b5b1bbf66f8f7a3a3fa2f9.js

200 ms

fusion-container-c734ee6a248ff59f9df588469658d997.js

fusion-container-c734ee6a248ff59f9df588469658d997.js

199 ms

fusion-responsive-typography-1c29471358d022bb3724315047fd9f93.js

fusion-responsive-typography-1c29471358d022bb3724315047fd9f93.js

197 ms

fusion-general-global-bb5b62264bde81f9283c7314c5a9f6c0.js

fusion-general-global-bb5b62264bde81f9283c7314c5a9f6c0.js

194 ms

fusion-video-6dc94bfdeed4f6e232c88073b75c4529.js

fusion-video-6dc94bfdeed4f6e232c88073b75c4529.js

194 ms

fusion-column-7de697ff543a190394df95445d380d4b.js

fusion-column-7de697ff543a190394df95445d380d4b.js

194 ms

lazyload.min.js

lazyload.min.js

182 ms

pinterest-pro.min.js

pinterest-pro.min.js

181 ms

subscribe-forms.min.js

subscribe-forms.min.js

181 ms

essb-core.min.js

essb-core.min.js

179 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXw.woff

366 ms

Accessibility Review

chasingplaces.com accessibility score

88

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

chasingplaces.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

chasingplaces.com SEO score

81

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

Links do not have descriptive text

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

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

chasingplaces.com

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