Tools & Wizards About Us
twillingate.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

twillingate.com

Twillingate - Stay, Dine and Enjoy a Show with us

Page Load Speed

3.8 sec in total

First Response

83 ms

Resources Loaded

2.7 sec

Page Rendered

1 sec

twillingate.com screenshot

About Website

Visit twillingate.com now to see the best up-to-date Twillingate content for Canada and also check out these interesting facts you probably never knew about twillingate.com

Twillingate - Stay, Dine and Enjoy a Show. Stay at Twillingate's boutique Hodge Premises Inn, the Anchor Inn Hotel, or the Alphabet Fleet Inn.

Visit twillingate.com

Key Findings

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

Performance Metrics

twillingate.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value11.3 s

0/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value5,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.17

70/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

twillingate.com

83 ms

twillingate.com

858 ms

js

222 ms

css

110 ms

style.min.css

84 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 77% of them (36 requests) were addressed to the original Twillingate.com, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (858 ms) belongs to the original domain Twillingate.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.3 kB (21%)

Content Size

377.2 kB

After Optimization

297.8 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Twillingate.com main page is 377.2 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. 55% of websites need less resources to load. Images take 257.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 78.7 kB

  • Original 96.0 kB
  • After minification 94.1 kB
  • After compression 17.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 78.7 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 566 B

  • Original 257.6 kB
  • After minification 257.1 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. Twillingate images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

Requests Breakdown

Number of requests can be reduced by 27 (68%)

Requests Now

40

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twillingate.com

twillingate.com

83 ms

twillingate.com

twillingate.com

858 ms

js

js

222 ms

css

css

110 ms

style.min.css

style.min.css

84 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

103 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

103 ms

simple-sitemap.css

simple-sitemap.css

102 ms

styles.css

styles.css

102 ms

style.css

style.css

103 ms

photoswipe.css

photoswipe.css

101 ms

default-skin.css

default-skin.css

196 ms

jetpack.css

jetpack.css

197 ms

jquery.min.js

jquery.min.js

230 ms

jquery-migrate.min.js

jquery-migrate.min.js

194 ms

wpgmza_data.js

wpgmza_data.js

193 ms

swipebox.min.css

swipebox.min.css

160 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

183 ms

wp-polyfill.min.js

wp-polyfill.min.js

195 ms

index.js

index.js

194 ms

photoswipe.min.js

photoswipe.min.js

194 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

268 ms

gallery.js

gallery.js

270 ms

all.js

all.js

528 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

269 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

269 ms

e-202240.js

e-202240.js

68 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

139 ms

fbevents.js

fbevents.js

171 ms

default-bg.jpg

default-bg.jpg

263 ms

search.svg

search.svg

92 ms

fb-logo.svg

fb-logo.svg

75 ms

tw-logo.svg

tw-logo.svg

75 ms

ig-logo.svg

ig-logo.svg

92 ms

Hodge-Premises-at-Dusk-350x233.jpg

Hodge-Premises-at-Dusk-350x233.jpg

125 ms

add.svg

add.svg

108 ms

Anchor-Inn-Hotel-Aerial-Tom-C-Small-350x234.jpg

Anchor-Inn-Hotel-Aerial-Tom-C-Small-350x234.jpg

139 ms

button-4.png

button-4.png

125 ms

IMG_4175-1-350x226.jpg

IMG_4175-1-350x226.jpg

136 ms

libel-suit-rg-webfont.woff

libel-suit-rg-webfont.woff

784 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

122 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

124 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

125 ms

analytics.js

analytics.js

114 ms

3012445055515528

3012445055515528

165 ms

collect

collect

167 ms

libel-suit-rg.woff

libel-suit-rg.woff

688 ms

Accessibility Review

twillingate.com accessibility score

89

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

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

twillingate.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

twillingate.com SEO score

84

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

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 Twillingate.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 Twillingate.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

twillingate.com

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