Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

pontoons.com

Award Winning Pontoon Boats and Tritoons Boats by Premier Marine

Page Load Speed

2.2 sec in total

First Response

376 ms

Resources Loaded

1.7 sec

Page Rendered

185 ms

About Website

Click here to check amazing Pontoon S content for United States. Otherwise, check out these important facts you probably never knew about pontoons.com

Premier Marine designs and manufactures the best pontoon boats on the water. Visit us today to learn more and find your local pontoon boat dealer.

Visit pontoons.com

Key Findings

We analyzed Pontoons.com page load time and found that the first response time was 376 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

pontoons.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.413

24/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

pontoons.com

376 ms

base.css

72 ms

style.css

138 ms

stylesheet.css

135 ms

jetmenu.css

140 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Pontoons.com, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (819 ms) belongs to the original domain Pontoons.com.

Page Optimization Overview & Recommendations

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

Content Size

4.1 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pontoons.com main page is 4.1 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. 45% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 31.5 kB

  • Original 35.9 kB
  • After minification 29.6 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 6.3 kB, which is 18% 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 31.5 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 16.7 kB

  • Original 3.5 MB
  • After minification 3.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. Pontoon S images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 249.2 kB

  • Original 365.9 kB
  • After minification 364.6 kB
  • After compression 116.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 249.2 kB or 68% of the original size.

CSS Optimization

-88%

Potential reduce by 153.1 kB

  • Original 173.6 kB
  • After minification 122.3 kB
  • After compression 20.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. Pontoons.com needs all CSS files to be minified and compressed as it can save up to 153.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (29%)

Requests Now

42

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

pontoons.com accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

pontoons.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pontoons.com SEO score

89

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

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 Pontoons.com 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 Pontoons.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

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