Tools & Wizards About Us
webehome.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

webehome.com

WeBeHome - Alarm and Smart Home supplier, worldwide

Page Load Speed

2.8 sec in total

First Response

281 ms

Resources Loaded

2.4 sec

Page Rendered

169 ms

webehome.com screenshot

About Website

Click here to check amazing We Be Home content for Greece. Otherwise, check out these important facts you probably never knew about webehome.com

WeBeHome - Smart Home and Alarm solution that increase safety, reduce risks, save time and improve well-being

Visit webehome.com

Key Findings

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

Performance Metrics

webehome.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.535

14/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

webehome.com

281 ms

en

679 ms

bootstrap.min.css

233 ms

carousel.css

344 ms

respond.js

431 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 98% of them (57 requests) were addressed to the original Webehome.com, 2% (1 request) were made to Policy.app.cookieinformation.com. The less responsive or slowest element that took the longest time to load (759 ms) belongs to the original domain Webehome.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.8 kB (22%)

Content Size

738.3 kB

After Optimization

576.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 45.7 kB

  • Original 64.4 kB
  • After minification 51.6 kB
  • After compression 18.7 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 12.7 kB, which is 20% 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 45.7 kB or 71% of the original size.

Image Optimization

-12%

Potential reduce by 48.0 kB

  • Original 413.8 kB
  • After minification 365.8 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, We Be Home needs image optimization as it can save up to 48.0 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-23%

Potential reduce by 45.0 kB

  • Original 199.6 kB
  • After minification 199.6 kB
  • After compression 154.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 45.0 kB or 23% of the original size.

CSS Optimization

-38%

Potential reduce by 23.1 kB

  • Original 60.5 kB
  • After minification 60.3 kB
  • After compression 37.4 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. Webehome.com needs all CSS files to be minified and compressed as it can save up to 23.1 kB or 38% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

38

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webehome.com

webehome.com

281 ms

en

en

679 ms

bootstrap.min.css

bootstrap.min.css

233 ms

carousel.css

carousel.css

344 ms

respond.js

respond.js

431 ms

common.js

common.js

432 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

651 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

647 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

667 ms

settings.css

settings.css

454 ms

WebShop07.css

WebShop07.css

541 ms

Public0006.css

Public0006.css

543 ms

PublicOnly0006.css

PublicOnly0006.css

564 ms

common.css

common.css

650 ms

theme_myabell0002.css

theme_myabell0002.css

649 ms

uc.js

uc.js

70 ms

WebResource.axd

WebResource.axd

681 ms

ScriptResource.axd

ScriptResource.axd

759 ms

ScriptResource.axd

ScriptResource.axd

654 ms

jsdebug

jsdebug

656 ms

PortalAppOnly007.css

PortalAppOnly007.css

658 ms

bootstrap.min.js

bootstrap.min.js

660 ms

us.png

us.png

108 ms

facebook.gif

facebook.gif

215 ms

empty1500x600.png

empty1500x600.png

216 ms

WeBeHome_iPhone_hand_400.png

WeBeHome_iPhone_hand_400.png

400 ms

z-wavelogo_product.png

z-wavelogo_product.png

216 ms

easy_start.png

easy_start.png

234 ms

control_with_app.png

control_with_app.png

290 ms

smarter_home.png

smarter_home.png

291 ms

icon_energi.png

icon_energi.png

294 ms

icon_ma_bra.png

icon_ma_bra.png

301 ms

icon_kamera.png

icon_kamera.png

322 ms

icon_larm.png

icon_larm.png

398 ms

icon_smart.png

icon_smart.png

399 ms

icon_spara_tid.png

icon_spara_tid.png

415 ms

icon_brand.png

icon_brand.png

415 ms

icon_minska_riskerna.png

icon_minska_riskerna.png

429 ms

z-wave_logo_w160.png

z-wave_logo_w160.png

508 ms

Copenhagen_blinds_black.png

Copenhagen_blinds_black.png

508 ms

ifttt_works_with.png

ifttt_works_with.png

508 ms

appstore125.png

appstore125.png

507 ms

android_app_on_play_logo_small.png

android_app_on_play_logo_small.png

515 ms

google_via_ifttt.png

google_via_ifttt.png

535 ms

alexa_via_ifttt.png

alexa_via_ifttt.png

616 ms

SecuritasLogo300.jpg

SecuritasLogo300.jpg

615 ms

telldus_technologies_160.jpg

telldus_technologies_160.jpg

615 ms

stockholm_camber_of_commerce_w200.png

stockholm_camber_of_commerce_w200.png

615 ms

facebook.png

facebook.png

622 ms

instagram.png

instagram.png

644 ms

linkedin.gif

linkedin.gif

722 ms

google.gif

google.gif

721 ms

logo_no_bottom_text_86x86.png

logo_no_bottom_text_86x86.png

512 ms

loader.gif

loader.gif

468 ms

timer.png

timer.png

472 ms

bullet.png

bullet.png

339 ms

large_left.png

large_left.png

416 ms

large_right.png

large_right.png

416 ms

Accessibility Review

webehome.com accessibility score

87

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

[aria-*] attributes do not match their roles

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

SEO Factors

webehome.com SEO score

77

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

High

robots.txt is not valid

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webehome.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Webehome.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

webehome.com

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