Tools & Wizards About Us
trentsevern.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

trentsevern.com

Web Hosting from HostPapa

Page Load Speed

11 sec in total

First Response

3.5 sec

Resources Loaded

7.2 sec

Page Rendered

378 ms

trentsevern.com screenshot

About Website

Click here to check amazing Trentsevern content for Canada. Otherwise, check out these important facts you probably never knew about trentsevern.com

TrentSevern.com is your single source for information on the Trent-Severn Waterway

Visit trentsevern.com

Key Findings

We analyzed Trentsevern.com page load time and found that the first response time was 3.5 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

trentsevern.com performance score

0

Network Requests Diagram

trentsevern.com

3456 ms

plugin.css

1261 ms

rokbox.css

1319 ms

debug.css

600 ms

grid-12.css

1918 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (75%)

Content Size

2.7 MB

After Optimization

682.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trentsevern.com main page is 2.7 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. 35% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 1.0 MB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 44.2 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 1.0 MB or 96% of the original size.

Image Optimization

-13%

Potential reduce by 57.6 kB

  • Original 453.8 kB
  • After minification 396.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, Trentsevern needs image optimization as it can save up to 57.6 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

-80%

Potential reduce by 836.6 kB

  • Original 1.0 MB
  • After minification 737.5 kB
  • After compression 204.6 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 836.6 kB or 80% of the original size.

CSS Optimization

-79%

Potential reduce by 142.7 kB

  • Original 180.2 kB
  • After minification 166.0 kB
  • After compression 37.5 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. Trentsevern.com needs all CSS files to be minified and compressed as it can save up to 142.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (54%)

Requests Now

85

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trentsevern.com

trentsevern.com

3456 ms

plugin.css

plugin.css

1261 ms

rokbox.css

rokbox.css

1319 ms

debug.css

debug.css

600 ms

grid-12.css

grid-12.css

1918 ms

gantry.css

gantry.css

1260 ms

joomla.css

joomla.css

778 ms

joomla.css

joomla.css

959 ms

master.css

master.css

1137 ms

demo-styles.css

demo-styles.css

1077 ms

template.css

template.css

1174 ms

template-firefox.css

template-firefox.css

1227 ms

template-gecko.css

template-gecko.css

1266 ms

overlays.css

overlays.css

1446 ms

typography.css

typography.css

1435 ms

fusionmenu.css

fusionmenu.css

1347 ms

roktabs.css

roktabs.css

1365 ms

mootools-core-uncompressed.js

mootools-core-uncompressed.js

2300 ms

core-uncompressed.js

core-uncompressed.js

1437 ms

mootools-more-uncompressed.js

mootools-more-uncompressed.js

2896 ms

rokbox.js

rokbox.js

1719 ms

jquery.js

jquery.js

3552 ms

jquery-noconflict.js

jquery-noconflict.js

1531 ms

jquery-migrate.js

jquery-migrate.js

1733 ms

bootstrap.js

bootstrap.js

1921 ms

gantry-rotator.js

gantry-rotator.js

1868 ms

gantry-morearticles.js

gantry-morearticles.js

1968 ms

gantry-smartload.js

gantry-smartload.js

1995 ms

gantry-inputs.js

gantry-inputs.js

2018 ms

browser-engines.js

browser-engines.js

2075 ms

fusion.js

fusion.js

2180 ms

roktabs.js

roktabs.js

2117 ms

countdown.js

countdown.js

2437 ms

header-bg.png

header-bg.png

593 ms

logo.png

logo.png

593 ms

menutop-daddy.png

menutop-daddy.png

594 ms

header-bg.png

header-bg.png

593 ms

dropdown-daddy.png

dropdown-daddy.png

594 ms

art-ceiling.jpg

art-ceiling.jpg

600 ms

showcase-overlay2.png

showcase-overlay2.png

595 ms

showcase-overlay.png

showcase-overlay.png

595 ms

showcase-preview.png

showcase-preview.png

596 ms

marina.jpg

marina.jpg

598 ms

sunsetboat.jpg

sunsetboat.jpg

595 ms

footer-trans.png

footer-trans.png

596 ms

shadow-l.png

shadow-l.png

596 ms

shadow-r.png

shadow-r.png

596 ms

rotator-controls.png

rotator-controls.png

597 ms

charts-frontpage.jpg

charts-frontpage.jpg

599 ms

readon-r.png

readon-r.png

597 ms

readon-l.png

readon-l.png

598 ms

featured-locks.jpg

featured-locks.jpg

599 ms

marinalocator-frontpage.jpg

marinalocator-frontpage.jpg

599 ms

featured-predepature.jpg

featured-predepature.jpg

599 ms

discussion_board.jpg

discussion_board.jpg

603 ms

lockfee.png

lockfee.png

600 ms

whatyoushouldknow.png

whatyoushouldknow.png

599 ms

photocontest.png

photocontest.png

600 ms

bottom-feature-girl.jpg

bottom-feature-girl.jpg

600 ms

bottom-featured-phone.jpg

bottom-featured-phone.jpg

600 ms

bottom-featured-ring.jpg

bottom-featured-ring.jpg

652 ms

facebook_icon.png

facebook_icon.png

601 ms

twitter_icon.png

twitter_icon.png

621 ms

youtube_icon.png

youtube_icon.png

622 ms

tabbg-light.png

tabbg-light.png

617 ms

tabbg-active-light.png

tabbg-active-light.png

626 ms

icon-check.png

icon-check.png

633 ms

footer-bg.png

footer-bg.png

648 ms

body-arrow.png

body-arrow.png

683 ms

moduleborder-r.png

moduleborder-r.png

157 ms

blank.gif

blank.gif

161 ms

spinner.gif

spinner.gif

177 ms

flipper00.png

flipper00.png

180 ms

flipper01.png

flipper01.png

184 ms

flipper02.png

flipper02.png

232 ms

flipper10.png

flipper10.png

206 ms

flipper11.png

flipper11.png

213 ms

flipper12.png

flipper12.png

230 ms

flipper20.png

flipper20.png

234 ms

flipper21.png

flipper21.png

234 ms

flipper22.png

flipper22.png

286 ms

flipper90.png

flipper90.png

296 ms

flipper91.png

flipper91.png

301 ms

flipper92.png

flipper92.png

321 ms

prev-light.png

prev-light.png

108 ms

next-light.png

next-light.png

97 ms

SEO Factors

trentsevern.com SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

trentsevern.com

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