Tools & Wizards About Us
tgl.co screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tgl.co

TGL | International Freight Forwarder | Complete Logistics

Page Load Speed

11 sec in total

First Response

1.1 sec

Resources Loaded

4.4 sec

Page Rendered

5.5 sec

tgl.co screenshot

About Website

Click here to check amazing TGL content. Otherwise, check out these important facts you probably never knew about tgl.co

Australian owned international freight forwarder providing solutions in sea, air, domestic freight, customs and warehousing. Making logistics personal.

Visit tgl.co

Key Findings

We analyzed Tgl.co page load time and found that the first response time was 1.1 sec and then it took 9.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

tgl.co performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value3,810 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value25.9 s

0/100

10%

Network Requests Diagram

tgl.co

1102 ms

eut.css

622 ms

51cceff7b0374870b9b441f8026cdadf.js

48 ms

js

67 ms

styles.6e84e3839ea859523204.css

1230 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 39% of them (34 requests) were addressed to the original Tgl.co, 41% (36 requests) were made to Cdn.buttercms.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Tgl.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 327.9 kB (9%)

Content Size

3.5 MB

After Optimization

3.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tgl.co main page is 3.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. 65% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 100.9 kB

  • Original 119.2 kB
  • After minification 115.5 kB
  • After compression 18.3 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 100.9 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 49.9 kB

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

JavaScript Optimization

-18%

Potential reduce by 126.8 kB

  • Original 704.3 kB
  • After minification 704.3 kB
  • After compression 577.5 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 126.8 kB or 18% of the original size.

CSS Optimization

-39%

Potential reduce by 50.3 kB

  • Original 128.3 kB
  • After minification 128.3 kB
  • After compression 77.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. Tgl.co needs all CSS files to be minified and compressed as it can save up to 50.3 kB or 39% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tgl.co

tgl.co

1102 ms

eut.css

eut.css

622 ms

51cceff7b0374870b9b441f8026cdadf.js

51cceff7b0374870b9b441f8026cdadf.js

48 ms

js

js

67 ms

styles.6e84e3839ea859523204.css

styles.6e84e3839ea859523204.css

1230 ms

js

js

66 ms

widget.css

widget.css

210 ms

widget.js

widget.js

406 ms

runtime.78896aea50583bd3bc16.js

runtime.78896aea50583bd3bc16.js

625 ms

polyfills.07b2f401bf7c2b78633c.js

polyfills.07b2f401bf7c2b78633c.js

736 ms

scripts.f6cdf9338e83eb5071be.js

scripts.f6cdf9338e83eb5071be.js

1266 ms

main.6820873a36adadd0fd4e.js

main.6820873a36adadd0fd4e.js

1862 ms

WebsiteAutomation.js

WebsiteAutomation.js

979 ms

js

js

58 ms

analytics.js

analytics.js

19 ms

js

js

83 ms

collect

collect

12 ms

collect

collect

58 ms

RdTo0s0tQvOhBDBpp8K8

RdTo0s0tQvOhBDBpp8K8

108 ms

V4e86j3TQIqU4K341oR4

V4e86j3TQIqU4K341oR4

119 ms

D8ICleztSFeUSC9kzuBl

D8ICleztSFeUSC9kzuBl

118 ms

DJisDRlaT0aocP6MLwAE

DJisDRlaT0aocP6MLwAE

114 ms

KHCOsEvMTu21lipzRGLw

KHCOsEvMTu21lipzRGLw

116 ms

HkoQNC4xRP6dbdrlGv2I

HkoQNC4xRP6dbdrlGv2I

120 ms

nK6V0nsT5eiCfaTvrw9k

nK6V0nsT5eiCfaTvrw9k

120 ms

HQ67RtTZTLO8cCGHILVe

HQ67RtTZTLO8cCGHILVe

126 ms

CrKTsBl4QPiPVYpAz2Uw

CrKTsBl4QPiPVYpAz2Uw

126 ms

HmLPbmB3TliqPgW79lFT

HmLPbmB3TliqPgW79lFT

122 ms

Fp6arqjTsaaWqTnzdm6w

Fp6arqjTsaaWqTnzdm6w

123 ms

ROAjBAKcQmeCYQATaA8F

ROAjBAKcQmeCYQATaA8F

124 ms

TzamGakaQ9aeMweIyEXM

TzamGakaQ9aeMweIyEXM

123 ms

XKlj9AVoSvG40BgtZEWA

XKlj9AVoSvG40BgtZEWA

134 ms

A0M1z969RpejWeYe1Fqj

A0M1z969RpejWeYe1Fqj

129 ms

v4N4vvBMSAyWHAgPVj9k

v4N4vvBMSAyWHAgPVj9k

128 ms

mokJ21mSW5VlVloWjALN

mokJ21mSW5VlVloWjALN

129 ms

4CEkiyglSZCXvPsMx7Cw

4CEkiyglSZCXvPsMx7Cw

130 ms

logo1.png

logo1.png

301 ms

Service-6.svg

Service-6.svg

353 ms

Service-7.svg

Service-7.svg

406 ms

Service-8.svg

Service-8.svg

510 ms

Service-9.svg

Service-9.svg

577 ms

Service-10.svg

Service-10.svg

618 ms

LinkedIn.png

LinkedIn.png

699 ms

YT.png

YT.png

716 ms

PC.png

PC.png

782 ms

FB.png

FB.png

822 ms

IG.png

IG.png

1107 ms

News-white.svg

News-white.svg

924 ms

News-navy.svg

News-navy.svg

935 ms

widget

widget

1374 ms

munchkin.js

munchkin.js

73 ms

j06sg29OSoiJhLbzDXF4

j06sg29OSoiJhLbzDXF4

20 ms

hOO7uNxKRgquNLvlZNNh

hOO7uNxKRgquNLvlZNNh

47 ms

m8nWw1SaT7azcJCPWwXF

m8nWw1SaT7azcJCPWwXF

47 ms

1ez92SAeXXiCWi0PeZg9

1ez92SAeXXiCWi0PeZg9

48 ms

jN1GTFWPTP6gQAxBnJnq

jN1GTFWPTP6gQAxBnJnq

46 ms

GuoVtUFtRbeVrLrrMIvV

GuoVtUFtRbeVrLrrMIvV

48 ms

PTzfbCGyQaZXhPw01dge

PTzfbCGyQaZXhPw01dge

45 ms

GmL3Gi9HQ4epCNPb0Oeg

GmL3Gi9HQ4epCNPb0Oeg

53 ms

4dimBs90Qz6EjIpRgGsS

4dimBs90Qz6EjIpRgGsS

54 ms

nhdPOe9pQveFz76GUtNu

nhdPOe9pQveFz76GUtNu

53 ms

jqJunOUvQChV1HRkPm7B

jqJunOUvQChV1HRkPm7B

53 ms

HQ67RtTZTLO8cCGHILVe

HQ67RtTZTLO8cCGHILVe

49 ms

Fp6arqjTsaaWqTnzdm6w

Fp6arqjTsaaWqTnzdm6w

52 ms

XKlj9AVoSvG40BgtZEWA

XKlj9AVoSvG40BgtZEWA

50 ms

A0M1z969RpejWeYe1Fqj

A0M1z969RpejWeYe1Fqj

55 ms

v4N4vvBMSAyWHAgPVj9k

v4N4vvBMSAyWHAgPVj9k

54 ms

mokJ21mSW5VlVloWjALN

mokJ21mSW5VlVloWjALN

55 ms

4CEkiyglSZCXvPsMx7Cw

4CEkiyglSZCXvPsMx7Cw

54 ms

port-with-grid-01.jpg

port-with-grid-01.jpg

1075 ms

home-hero-bottom-mask-02.svg

home-hero-bottom-mask-02.svg

499 ms

tgl-logo-grey.svg

tgl-logo-grey.svg

1012 ms

world-map-02.jpg

world-map-02.jpg

808 ms

pillars-1.svg

pillars-1.svg

1735 ms

pillars-2.svg

pillars-2.svg

983 ms

pillars-3.svg

pillars-3.svg

1005 ms

pillars-4.svg

pillars-4.svg

1010 ms

pillars-5.svg

pillars-5.svg

1187 ms

quote.svg

quote.svg

1212 ms

top-mask-00.svg

top-mask-00.svg

1214 ms

background-no-mask.svg

background-no-mask.svg

1219 ms

arrow-toward-right.svg

arrow-toward-right.svg

1245 ms

Muli.4829cf81e2b513fc1b64.ttf

Muli.4829cf81e2b513fc1b64.ttf

1354 ms

insight.min.js

insight.min.js

38 ms

munchkin.js

munchkin.js

16 ms

visitWebPage

visitWebPage

446 ms

insight_tag_errors.gif

insight_tag_errors.gif

47 ms

Accessibility Review

tgl.co accessibility score

91

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

tgl.co 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

tgl.co SEO score

92

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 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 Tgl.co 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 Tgl.co 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

tgl.co

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