Tools & Wizards About Us
zump.me screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

zump.me

Zump Property | A Better Way To Find Your Next Home | Bristol

Page Load Speed

21.3 sec in total

First Response

132 ms

Resources Loaded

21.1 sec

Page Rendered

56 ms

zump.me screenshot

About Website

Click here to check amazing Zump content. Otherwise, check out these important facts you probably never knew about zump.me

Try the all in one property app that gives you more homes to search from, and an easier first step to selling your property.

Visit zump.me

Key Findings

We analyzed Zump.me page load time and found that the first response time was 132 ms and then it took 21.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

zump.me performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

www.zump.me

132 ms

originTrials.41d7301a.bundle.min.js

33 ms

minified.js

36 ms

focus-within-polyfill.js

71 ms

polyfill.min.js

19680 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zump.me, 48% (32 requests) were made to Static.wixstatic.com and 27% (18 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 926.9 kB (53%)

Content Size

1.7 MB

After Optimization

821.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Zump.me main page is 1.7 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. HTML takes 891.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 730.8 kB

  • Original 891.1 kB
  • After minification 889.4 kB
  • After compression 160.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 730.8 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 42.2 kB

  • Original 477.6 kB
  • After minification 435.4 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. Zump images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 153.8 kB

  • Original 379.3 kB
  • After minification 379.2 kB
  • After compression 225.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 153.8 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (24%)

Requests Now

45

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.zump.me

www.zump.me

132 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

33 ms

minified.js

minified.js

36 ms

focus-within-polyfill.js

focus-within-polyfill.js

71 ms

polyfill.min.js

polyfill.min.js

19680 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

71 ms

thunderbolt-commons.1e70fbb2.bundle.min.js

thunderbolt-commons.1e70fbb2.bundle.min.js

46 ms

main.42e492e1.bundle.min.js

main.42e492e1.bundle.min.js

53 ms

lodash.min.js

lodash.min.js

54 ms

react.production.min.js

react.production.min.js

51 ms

react-dom.production.min.js

react-dom.production.min.js

53 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

52 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

53 ms

logo-18.png

logo-18.png

219 ms

Group%202137.png

Group%202137.png

334 ms

CIRCLE.png

CIRCLE.png

399 ms

TOP%20HEADER%20Screen2.png

TOP%20HEADER%20Screen2.png

397 ms

505031_d5501bb7da654969b0e500ad50514835~mv2.png

505031_d5501bb7da654969b0e500ad50514835~mv2.png

371 ms

e6f9c8_125136cfa9754ca984052ab08ab08a21~mv2.png

e6f9c8_125136cfa9754ca984052ab08ab08a21~mv2.png

361 ms

Trustpilot_brandmark_gr-blk-RGB.png

Trustpilot_brandmark_gr-blk-RGB.png

336 ms

Trustpilot_ratings_5star-RGB-512x96.png

Trustpilot_ratings_5star-RGB-512x96.png

476 ms

HM_Land_Registry.png

HM_Land_Registry.png

505 ms

5a451923-593d-43df-a22b-0288aa9cac62-siz.png

5a451923-593d-43df-a22b-0288aa9cac62-siz.png

508 ms

361293663_662885289188372_7773581950683550231_n_edited.jpg

361293663_662885289188372_7773581950683550231_n_edited.jpg

527 ms

Group%202153.png

Group%202153.png

551 ms

Group%202156.png

Group%202156.png

602 ms

Group%202160.png

Group%202160.png

670 ms

Group%202158.png

Group%202158.png

675 ms

Group%202162a.png

Group%202162a.png

677 ms

e6f9c8_b76f952a8aeb4455a3ba99f59aeff992~mv2.png

e6f9c8_b76f952a8aeb4455a3ba99f59aeff992~mv2.png

691 ms

e6f9c8_a7ab2a44fe4543af941700f57573bb9a~mv2.png

e6f9c8_a7ab2a44fe4543af941700f57573bb9a~mv2.png

746 ms

e6f9c8_f42841a9404947ceab5fb79773a91e7e~mv2.png

e6f9c8_f42841a9404947ceab5fb79773a91e7e~mv2.png

785 ms

e6f9c8_67eb185d63a142d183279cd120dd1e23~mv2.png

e6f9c8_67eb185d63a142d183279cd120dd1e23~mv2.png

896 ms

e6f9c8_86f1a13750b24204b9e35482b6afcc8f~mv2.png

e6f9c8_86f1a13750b24204b9e35482b6afcc8f~mv2.png

799 ms

e6f9c8_f62798703caa407e8d9411fe9ce66411~mv2.png

e6f9c8_f62798703caa407e8d9411fe9ce66411~mv2.png

850 ms

e6f9c8_0201c381866d4956a83cc277f533d904~mv2.png

e6f9c8_0201c381866d4956a83cc277f533d904~mv2.png

907 ms

e6f9c8_f2578a7c199e46389c9ce5f183e9e5aa~mv2.png

e6f9c8_f2578a7c199e46389c9ce5f183e9e5aa~mv2.png

906 ms

e6f9c8_9f473102d8f74f7d8e40b0f16dd74c40~mv2.png

e6f9c8_9f473102d8f74f7d8e40b0f16dd74c40~mv2.png

953 ms

e6f9c8_377024bc13c14aeab125e90f83217e38~mv2.png

e6f9c8_377024bc13c14aeab125e90f83217e38~mv2.png

981 ms

e6f9c8_b44516518aad4a6eb15a4151b5c42e44~mv2.png

e6f9c8_b44516518aad4a6eb15a4151b5c42e44~mv2.png

994 ms

Trustpilot_ratings_5star-RGB-512x96.png

Trustpilot_ratings_5star-RGB-512x96.png

1001 ms

Trustpilot_brandmark_gr-blk-RGB.png

Trustpilot_brandmark_gr-blk-RGB.png

1022 ms

bundle.min.js

bundle.min.js

95 ms

file.woff

file.woff

726 ms

file.woff

file.woff

743 ms

03805817-4611-4dbc-8c65-0f73031c3973.woff

03805817-4611-4dbc-8c65-0f73031c3973.woff

50 ms

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff

34 ms

file.woff

file.woff

743 ms

45 ms

7 ms

9 ms

8 ms

10 ms

10 ms

48 ms

50 ms

49 ms

50 ms

51 ms

88 ms

deprecation-en.v5.html

deprecation-en.v5.html

5 ms

bolt-performance

bolt-performance

16 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

9 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

4 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

4 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

4 ms

Accessibility Review

zump.me accessibility score

97

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

zump.me 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

zump.me SEO score

96

Search Engine Optimization Advices

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 Zump.me 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 Zump.me 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

zump.me

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