Tools & Wizards About Us
whitehorse.co.id screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whitehorse.co.id

Beranda - White Horse | Sewa Bus | Harga Bus Pariwisata

Page Load Speed

15.3 sec in total

First Response

1.6 sec

Resources Loaded

13.5 sec

Page Rendered

141 ms

whitehorse.co.id screenshot

About Website

Click here to check amazing White Horse content for Indonesia. Otherwise, check out these important facts you probably never knew about whitehorse.co.id

White Horse Group yang juga dikenal sebagai PT. WEHA Transportasi Indonesia, Tbk. adalah perusahaan publik yang terdaftar (JAK: WEHA) dengan bisnis utama di bidang transportasi darat dan memegang sert...

Visit whitehorse.co.id

Key Findings

We analyzed Whitehorse.co.id page load time and found that the first response time was 1.6 sec and then it took 13.6 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

whitehorse.co.id performance score

0

Network Requests Diagram

1615 ms

widgetkit.css

488 ms

style.css

489 ms

style.css

490 ms

style.css

495 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that all of those requests were addressed to Whitehorse.co.id and no external sources were called. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Whitehorse.co.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 713.3 kB (40%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whitehorse.co.id main page is 1.8 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. 30% of websites need less resources to load. Images take 968.4 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 36.3 kB

  • Original 44.0 kB
  • After minification 40.5 kB
  • After compression 7.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. 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 36.3 kB or 83% of the original size.

Image Optimization

-13%

Potential reduce by 124.0 kB

  • Original 968.4 kB
  • After minification 844.4 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. Obviously, White Horse needs image optimization as it can save up to 124.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-72%

Potential reduce by 463.4 kB

  • Original 641.4 kB
  • After minification 604.4 kB
  • After compression 178.0 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 463.4 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 89.6 kB

  • Original 109.5 kB
  • After minification 81.0 kB
  • After compression 19.9 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. Whitehorse.co.id needs all CSS files to be minified and compressed as it can save up to 89.6 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

78

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1615 ms

widgetkit.css

widgetkit.css

488 ms

style.css

style.css

489 ms

style.css

style.css

490 ms

style.css

style.css

495 ms

style.css

style.css

501 ms

style.css

style.css

729 ms

style.css

style.css

974 ms

style.css

style.css

975 ms

lightbox.css

lightbox.css

1000 ms

mediaelementplayer.css

mediaelementplayer.css

995 ms

style.css

style.css

1002 ms

style.css

style.css

1245 ms

style.css

style.css

1456 ms

style.css

style.css

1476 ms

style.css

style.css

1497 ms

style.css

style.css

1521 ms

style.css

style.css

1519 ms

style.css

style.css

1747 ms

spotlight.css

spotlight.css

1940 ms

style.css

style.css

1974 ms

style.css

style.css

2109 ms

default_icemegamenu.css

default_icemegamenu.css

2096 ms

template.css

template.css

2085 ms

style2.0.css

style2.0.css

2300 ms

mootools-core.js

mootools-core.js

3198 ms

core.js

core.js

2473 ms

caption.js

caption.js

2582 ms

jquery.js

jquery.js

3378 ms

jquery.plugins.js

jquery.plugins.js

2609 ms

responsive.js

responsive.js

2800 ms

accordion.js

accordion.js

2986 ms

lazyloader.js

lazyloader.js

3084 ms

lazyloader.js

lazyloader.js

3091 ms

lazyloader.js

lazyloader.js

3308 ms

lazyloader.js

lazyloader.js

3469 ms

template.css

template.css

3347 ms

twitter.js

twitter.js

3112 ms

mootools-more.js

mootools-more.js

4236 ms

engine.js

engine.js

3360 ms

icemegamenu.js

icemegamenu.js

3628 ms

jquery.simplemodal.js

jquery.simplemodal.js

3501 ms

default.js

default.js

3357 ms

template.js

template.js

3129 ms

lightbox.js

lightbox.js

950 ms

mediaelement-and-player.js

mediaelement-and-player.js

1010 ms

spotlight.js

spotlight.js

498 ms

stylesheet.css

stylesheet.css

515 ms

stylesheet.css

stylesheet.css

525 ms

searchButton.gif

searchButton.gif

491 ms

FP001.jpg

FP001.jpg

1389 ms

online_book_whdc.jpg

online_book_whdc.jpg

1717 ms

online_book_daytrans.jpg

online_book_daytrans.jpg

1876 ms

banner-web-imlek.jpg

banner-web-imlek.jpg

2042 ms

LOGO-TUV.png

LOGO-TUV.png

1919 ms

panorama.png

panorama.png

977 ms

loading.gif

loading.gif

1456 ms

notice-info.png

notice-info.png

1886 ms

top2-bg.png

top2-bg.png

1972 ms

shadow2.png

shadow2.png

2210 ms

logo.png

logo.png

2435 ms

border-r.png

border-r.png

2371 ms

nav.png

nav.png

2413 ms

arrow1.png

arrow1.png

2522 ms

head-bg.png

head-bg.png

2501 ms

shadow3.png

shadow3.png

2697 ms

border-bot.png

border-bot.png

2861 ms

pdf.png

pdf.png

2897 ms

shadow4.png

shadow4.png

2927 ms

BPreplay-webfont.woff

BPreplay-webfont.woff

3519 ms

slideshow.js

slideshow.js

2623 ms

fb.png

fb.png

2839 ms

tw.png

tw.png

2973 ms

border-bot2.png

border-bot2.png

3001 ms

friz_quadrata_bt-webfont.woff

friz_quadrata_bt-webfont.woff

3495 ms

FP006.jpg

FP006.jpg

2464 ms

FP003.jpg

FP003.jpg

1710 ms

FP004-edit.jpg

FP004-edit.jpg

1799 ms

FP005.jpg

FP005.jpg

2345 ms

SEO Factors

whitehorse.co.id SEO score

0

Language and Encoding

  • Language Detected

    ID

  • Language Claimed

    ID

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whitehorse.co.id can be misinterpreted by Google and other search engines. Our service has detected that is used on the page, and it matches the claimed language. Our system also found out that Whitehorse.co.id 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

whitehorse.co.id

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