Tools & Wizards About Us
viewings.properties screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

viewings.properties

Home - Viewings

Page Load Speed

2.1 sec in total

First Response

127 ms

Resources Loaded

889 ms

Page Rendered

1 sec

viewings.properties screenshot

About Website

Visit viewings.properties now to see the best up-to-date Viewings content and also check out these interesting facts you probably never knew about viewings.properties

Who Knows Your Property Better Than You? Viewings is a extensive property network that brings you all the tools regular agents use to sell your home. Explore the power of selling your property without...

Visit viewings.properties

Key Findings

We analyzed Viewings.properties page load time and found that the first response time was 127 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

viewings.properties performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

59/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

www.myviewings.co.uk

127 ms

style.min.css

22 ms

frontend.min.css

30 ms

swiper.min.css

40 ms

e-swiper.min.css

34 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Viewings.properties, 18% (12 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Myviewings.co.uk.

Page Optimization Overview & Recommendations

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

Content Size

903.2 kB

After Optimization

683.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viewings.properties main page is 903.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. 65% of websites need less resources to load. Javascripts take 503.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 131.8 kB

  • Original 159.1 kB
  • After minification 142.0 kB
  • After compression 27.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 17.0 kB, which is 11% 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 131.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 79.1 kB
  • After minification 79.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. Viewings images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 86.0 kB

  • Original 503.6 kB
  • After minification 503.6 kB
  • After compression 417.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 86.0 kB or 17% of the original size.

CSS Optimization

-1%

Potential reduce by 1.9 kB

  • Original 161.6 kB
  • After minification 161.5 kB
  • After compression 159.7 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. Viewings.properties has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 45 (87%)

Requests Now

52

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.myviewings.co.uk

www.myviewings.co.uk

127 ms

style.min.css

style.min.css

22 ms

frontend.min.css

frontend.min.css

30 ms

swiper.min.css

swiper.min.css

40 ms

e-swiper.min.css

e-swiper.min.css

34 ms

post-10.css

post-10.css

26 ms

fadeIn.min.css

fadeIn.min.css

31 ms

widget-spacer.min.css

widget-spacer.min.css

44 ms

widget-divider.min.css

widget-divider.min.css

47 ms

widget-heading.min.css

widget-heading.min.css

47 ms

fadeInRight.min.css

fadeInRight.min.css

45 ms

widget-image.min.css

widget-image.min.css

54 ms

houzez-studio-public.css

houzez-studio-public.css

55 ms

style.min.css

style.min.css

87 ms

latest.css

latest.css

90 ms

all-css.css

all-css.css

64 ms

all.min.css

all.min.css

98 ms

style.css

style.css

100 ms

gdpr-main.css

gdpr-main.css

94 ms

css

css

44 ms

jquery.min.js

jquery.min.js

99 ms

jquery-migrate.min.js

jquery-migrate.min.js

99 ms

houzez-studio-public.js

houzez-studio-public.js

100 ms

email-decode.min.js

email-decode.min.js

96 ms

coblocks-animation.js

coblocks-animation.js

98 ms

tiny-swiper.js

tiny-swiper.js

99 ms

coblocks-tinyswiper-initializer.js

coblocks-tinyswiper-initializer.js

100 ms

jquery.form.min.js

jquery.form.min.js

99 ms

all-scripts.js

all-scripts.js

103 ms

houzez-instant-page.js

houzez-instant-page.js

478 ms

core.min.js

core.min.js

108 ms

menu.min.js

menu.min.js

142 ms

dom-ready.min.js

dom-ready.min.js

105 ms

hooks.min.js

hooks.min.js

118 ms

i18n.min.js

i18n.min.js

124 ms

a11y.min.js

a11y.min.js

128 ms

autocomplete.min.js

autocomplete.min.js

126 ms

api.js

api.js

42 ms

mouse.min.js

mouse.min.js

144 ms

slider.min.js

slider.min.js

124 ms

jquery.vide.min.js

jquery.vide.min.js

127 ms

custom.min.js

custom.min.js

118 ms

main.js

main.js

441 ms

tti.min.js

tti.min.js

10 ms

css

css

43 ms

style.css

style.css

72 ms

Viewings.png

Viewings.png

52 ms

lazyloader-1.gif

lazyloader-1.gif

53 ms

cropped-V.png

cropped-V.png

54 ms

Viewings-2-1.png

Viewings-2-1.png

53 ms

gdpr-logo.png

gdpr-logo.png

52 ms

recaptcha__en.js

recaptcha__en.js

46 ms

scc-c2.min.js

scc-c2.min.js

24 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

80 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

80 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

119 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

130 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

133 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

132 ms

houzez-iconfont.ttf

houzez-iconfont.ttf

134 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

133 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

133 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

132 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

131 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

133 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

167 ms

Accessibility Review

viewings.properties accessibility score

68

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.

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

Low

No form fields have multiple labels

High

Links do not have a discernible name

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.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

viewings.properties best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

viewings.properties SEO score

83

Search Engine Optimization Advices

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 Viewings.properties 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 Viewings.properties 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

viewings.properties

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