Tools & Wizards About Us
thru.my screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

thru.my

jQuery Insert HTML inside an iFrame

Page Load Speed

13.8 sec in total

First Response

1.7 sec

Resources Loaded

11.9 sec

Page Rendered

225 ms

thru.my screenshot

About Website

Welcome to thru.my homepage info - get ready to check Thru best content for Malaysia right away, or after learning these important things about thru.my

Visit thru.my

Key Findings

We analyzed Thru.my page load time and found that the first response time was 1.7 sec and then it took 12.1 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

thru.my performance score

0

Network Requests Diagram

thru.my

1668 ms

wp-emoji-release.min.js

429 ms

style.css

4850 ms

dynamicCss.php

3810 ms

jquery.js

5205 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 86% of them (37 requests) were addressed to the original Thru.my, 5% (2 requests) were made to Apis.google.com and 5% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Thru.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.4 kB (66%)

Content Size

469.8 kB

After Optimization

158.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thru.my main page is 469.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 306.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.7 kB

  • Original 30.4 kB
  • After minification 29.7 kB
  • After compression 6.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 23.7 kB or 78% of the original size.

Image Optimization

-18%

Potential reduce by 9.7 kB

  • Original 54.1 kB
  • After minification 44.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, Thru needs image optimization as it can save up to 9.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 211.2 kB

  • Original 306.9 kB
  • After minification 288.0 kB
  • After compression 95.7 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 211.2 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 66.7 kB

  • Original 78.5 kB
  • After minification 60.1 kB
  • After compression 11.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. Thru.my needs all CSS files to be minified and compressed as it can save up to 66.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (43%)

Requests Now

42

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thru.my

thru.my

1668 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

429 ms

style.css

style.css

4850 ms

dynamicCss.php

dynamicCss.php

3810 ms

jquery.js

jquery.js

5205 ms

jquery-migrate.min.js

jquery-migrate.min.js

1027 ms

cufon-yui.js

cufon-yui.js

3048 ms

Colaborate-Thin_400.font.js

Colaborate-Thin_400.font.js

4688 ms

Colaborate-Regular_400.font.js

Colaborate-Regular_400.font.js

5774 ms

Colaborate-Bold_400.font.js

Colaborate-Bold_400.font.js

4592 ms

Miama_400.font.js

Miama_400.font.js

6609 ms

cufonJs.php

cufonJs.php

5505 ms

jqueryslidemenu.js

jqueryslidemenu.js

5429 ms

jquery.tools.tabs.min.js

jquery.tools.tabs.min.js

5488 ms

jquery.imgpreload.js

jquery.imgpreload.js

5550 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

5920 ms

jquery.quicksand.js

jquery.quicksand.js

6173 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

6175 ms

custom.js

custom.js

6316 ms

menuGradient.png

menuGradient.png

359 ms

navBorder-dark.png

navBorder-dark.png

273 ms

header-tealSkies.jpg

header-tealSkies.jpg

3633 ms

facebookIcon.png

facebookIcon.png

359 ms

emailIcon.png

emailIcon.png

296 ms

logo.png

logo.png

610 ms

noPageTitleBg.png

noPageTitleBg.png

801 ms

link-divider-blackandwhite.png

link-divider-blackandwhite.png

915 ms

inboxdelivery.jpg

inboxdelivery.jpg

917 ms

bluePreloader.gif

bluePreloader.gif

914 ms

shadow10.png

shadow10.png

1010 ms

tracking.jpg

tracking.jpg

1271 ms

kempen.jpg

kempen.jpg

1461 ms

analytic.jpg

analytic.jpg

1367 ms

tealSkiesEndOfContent.png

tealSkiesEndOfContent.png

1483 ms

footer-tealSkies.jpg

footer-tealSkies.jpg

3536 ms

plusone.js

plusone.js

63 ms

all.js

all.js

270 ms

loading.gif

loading.gif

2206 ms

controls.png

controls.png

2228 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

138 ms

xd_arbiter.php

xd_arbiter.php

215 ms

xd_arbiter.php

xd_arbiter.php

420 ms

SEO Factors

thru.my SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thru.my can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Thru.my 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

thru.my

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