Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tg.org

Home - Trellis Company

Page Load Speed

1.6 sec in total

First Response

149 ms

Resources Loaded

1.2 sec

Page Rendered

239 ms

tg.org screenshot

About Website

Click here to check amazing Tg content for United States. Otherwise, check out these important facts you probably never knew about tg.org

Trellis Company assists institutions with custom solutions to understand enrollment management, student success, and the student experience to fulfill their institutional mission.

Visit tg.org

Key Findings

We analyzed Tg.org page load time and found that the first response time was 149 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

tg.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.438

21/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

www.trelliscompany.org

149 ms

category-to-pages-wud.css

36 ms

jquery.ctp_wud.css

58 ms

cookie-law-info-public.css

64 ms

cookie-law-info-gdpr.css

64 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tg.org, 9% (10 requests) were made to Use.typekit.net and 4% (5 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (467 ms) relates to the external source Trelliscompany.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.5 kB (11%)

Content Size

1.4 MB

After Optimization

1.3 MB

In fact, the total size of Tg.org main page is 1.4 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 620.6 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 130.0 kB

  • Original 155.3 kB
  • After minification 152.0 kB
  • After compression 25.4 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 130.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 4.2 kB

  • Original 620.6 kB
  • After minification 616.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. Tg images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.7 kB

  • Original 356.4 kB
  • After minification 355.9 kB
  • After compression 350.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 8.7 kB

  • Original 278.2 kB
  • After minification 278.1 kB
  • After compression 269.6 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. Tg.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

103

After Optimization

15

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

Accessibility Review

tg.org accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

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

tg.org 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tg.org SEO score

93

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

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 Tg.org 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 Tg.org 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

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