Tools & Wizards About Us
maplehouse.com screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

maplehouse.com

Page Load Speed

443 ms in total

First Response

92 ms

Resources Loaded

174 ms

Page Rendered

177 ms

maplehouse.com screenshot

About Website

Click here to check amazing Maplehouse content. Otherwise, check out these important facts you probably never knew about maplehouse.com

Vancouver Bed and Breakfast in Kitsilano. Just a block from the beach and Vancouver's most popular beach park Maple Beach B&B is a lovingly restored circa 1900 Heritage Home. Located in the friendly V...

Visit maplehouse.com

Key Findings

We analyzed Maplehouse.com page load time and found that the first response time was 92 ms and then it took 351 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

maplehouse.com performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value4.0 s

87/100

10%

Network Requests Diagram

maplehouse.com

92 ms

csslib.css

4 ms

ga.js

3 ms

bgrnd_2.gif

11 ms

__utm.gif

11 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 88% of them (14 requests) were addressed to the original Maplehouse.com, 13% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (92 ms) belongs to the original domain Maplehouse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.3 kB (24%)

Content Size

26.3 kB

After Optimization

20.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Maplehouse.com main page is 26.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. Only 10% of websites need less resources to load. Javascripts take 17.2 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 5.1 kB

  • Original 7.6 kB
  • After minification 7.0 kB
  • After compression 2.6 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 5.1 kB or 67% of the original size.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-79%

Potential reduce by 1.1 kB

  • Original 1.4 kB
  • After minification 1.2 kB
  • After compression 299 B

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. Maplehouse.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maplehouse. According to our analytics all requests are already optimized.

Network Requests Diagram

maplehouse.com

maplehouse.com

92 ms

csslib.css

csslib.css

4 ms

ga.js

ga.js

3 ms

bgrnd_2.gif

bgrnd_2.gif

11 ms

__utm.gif

__utm.gif

11 ms

shim.gif

shim.gif

6 ms

new_logo.gif

new_logo.gif

14 ms

home.gif

home.gif

10 ms

facilities.gif

facilities.gif

8 ms

location.gif

location.gif

12 ms

reservations.gif

reservations.gif

8 ms

btn-vtour.gif

btn-vtour.gif

11 ms

click_here.gif

click_here.gif

9 ms

jpnflag.gif

jpnflag.gif

11 ms

japanese.gif

japanese.gif

11 ms

click_here_on.gif

click_here_on.gif

4 ms

Accessibility Review

maplehouse.com accessibility score

86

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

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

High

Page has valid source maps

SEO Factors

maplehouse.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maplehouse.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Maplehouse.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

maplehouse.com

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