Tools & Wizards About Us
tressleworks.ca screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tressleworks.ca

Tressleworks > Home

Page Load Speed

1.5 sec in total

First Response

279 ms

Resources Loaded

1.1 sec

Page Rendered

97 ms

tressleworks.ca screenshot

About Website

Visit tressleworks.ca now to see the best up-to-date Tressleworks content and also check out these interesting facts you probably never knew about tressleworks.ca

Tressleworks.ca DotNetNuke Module Development and Site Management

Visit tressleworks.ca

Key Findings

We analyzed Tressleworks.ca page load time and found that the first response time was 279 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

tressleworks.ca performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

www.tressleworks.ca

279 ms

default.css

97 ms

module.css

82 ms

SearchSkinObjectPreview.css

74 ms

skin.css

84 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original Tressleworks.ca, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (289 ms) belongs to the original domain Tressleworks.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 249.8 kB (46%)

Content Size

537.3 kB

After Optimization

287.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tressleworks.ca main page is 537.3 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. 50% of websites need less resources to load. Javascripts take 413.5 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 20.3 kB

  • Original 31.2 kB
  • After minification 27.2 kB
  • After compression 10.9 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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 20.3 kB or 65% of the original size.

Image Optimization

-13%

Potential reduce by 4.9 kB

  • Original 39.1 kB
  • After minification 34.2 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, Tressleworks needs image optimization as it can save up to 4.9 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

-48%

Potential reduce by 200.1 kB

  • Original 413.5 kB
  • After minification 413.5 kB
  • After compression 213.3 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 200.1 kB or 48% of the original size.

CSS Optimization

-46%

Potential reduce by 24.5 kB

  • Original 53.5 kB
  • After minification 51.8 kB
  • After compression 29.0 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. Tressleworks.ca needs all CSS files to be minified and compressed as it can save up to 24.5 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (74%)

Requests Now

43

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tressleworks. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.tressleworks.ca

www.tressleworks.ca

279 ms

default.css

default.css

97 ms

module.css

module.css

82 ms

SearchSkinObjectPreview.css

SearchSkinObjectPreview.css

74 ms

skin.css

skin.css

84 ms

container.css

container.css

81 ms

portal.css

portal.css

76 ms

jquery.js

jquery.js

261 ms

jquery-migrate.js

jquery-migrate.js

119 ms

jquery-ui.js

jquery-ui.js

289 ms

WebResource.axd

WebResource.axd

119 ms

Slide.js

Slide.js

141 ms

StandardMenu.js

StandardMenu.js

133 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

226 ms

dnn.js

dnn.js

164 ms

dnn.modalpopup.js

dnn.modalpopup.js

174 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

185 ms

dnn.servicesframework.js

dnn.servicesframework.js

208 ms

dnn.jquery.js

dnn.jquery.js

261 ms

SearchSkinObjectPreview.js

SearchSkinObjectPreview.js

224 ms

dnncore.js

dnncore.js

248 ms

bootstrap.js

bootstrap.js

271 ms

scrolltop.js

scrolltop.js

264 ms

Search.js

Search.js

261 ms

initWidgets.js

initWidgets.js

270 ms

bootstrap.css

bootstrap.css

237 ms

css

css

21 ms

TW_400.png

TW_400.png

47 ms

Action_16X16_Standard.png

Action_16X16_Standard.png

45 ms

bottom-tile.gif

bottom-tile.gif

47 ms

LoginLinksBg.png

LoginLinksBg.png

51 ms

search_bg.jpg

search_bg.jpg

52 ms

menu_bg.jpg

menu_bg.jpg

46 ms

menu_sep.jpg

menu_sep.jpg

56 ms

menu_hover.jpg

menu_hover.jpg

56 ms

content_bg.jpg

content_bg.jpg

44 ms

banner_shadow.png

banner_shadow.png

57 ms

left_shadow.png

left_shadow.png

57 ms

right_shadow.png

right_shadow.png

68 ms

bread_icon.jpg

bread_icon.jpg

73 ms

c3_line.jpg

c3_line.jpg

71 ms

footer_bg.jpg

footer_bg.jpg

74 ms

pane_sep.png

pane_sep.png

93 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

29 ms

DotNetNukeAjaxShared.js

DotNetNukeAjaxShared.js

79 ms

DnnSearch_16X16_Standard.png

DnnSearch_16X16_Standard.png

73 ms

Accessibility Review

tressleworks.ca accessibility score

96

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.

Best Practices

tressleworks.ca best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Browser errors were logged to the console

SEO Factors

tressleworks.ca SEO score

90

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

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 Tressleworks.ca 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 Tressleworks.ca 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

tressleworks.ca

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