Tools & Wizards About Us
further.space screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

further.space

FurtherSpace - Glamping Northern Ireland & Scotland

Page Load Speed

1.6 sec in total

First Response

121 ms

Resources Loaded

1.4 sec

Page Rendered

86 ms

further.space screenshot

About Website

Visit further.space now to see the best up-to-date Further content and also check out these interesting facts you probably never knew about further.space

FURTHER.SPACE offer glamping holidays with a difference in Ireland & Scotland with luxury glamping pods in woodland, farm & lakeside settings.

Visit further.space

Key Findings

We analyzed Further.space page load time and found that the first response time was 121 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

further.space performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.299

40/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

further.space

121 ms

further.space

150 ms

banner.js

30 ms

way7yzg.css

80 ms

theme.min.css

26 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 72% of them (54 requests) were addressed to the original Further.space, 9% (7 requests) were made to Use.typekit.net and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (623 ms) belongs to the original domain Further.space.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.1 kB (8%)

Content Size

358.4 kB

After Optimization

329.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Further.space main page is 358.4 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. 60% of websites need less resources to load. Javascripts take 243.3 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.1 kB

  • Original 34.8 kB
  • After minification 34.7 kB
  • After compression 7.8 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 27.1 kB or 78% of the original size.

JavaScript Optimization

-0%

Potential reduce by 560 B

  • Original 243.3 kB
  • After minification 243.3 kB
  • After compression 242.8 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

-2%

Potential reduce by 1.5 kB

  • Original 80.3 kB
  • After minification 80.3 kB
  • After compression 78.8 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. Further.space has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (90%)

Requests Now

63

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

further.space

further.space

121 ms

further.space

further.space

150 ms

banner.js

banner.js

30 ms

way7yzg.css

way7yzg.css

80 ms

theme.min.css

theme.min.css

26 ms

style.css

style.css

146 ms

style.min.css

style.min.css

145 ms

header-footer.min.css

header-footer.min.css

132 ms

frontend-lite.min.css

frontend-lite.min.css

38 ms

post-5.css

post-5.css

45 ms

all.min.css

all.min.css

49 ms

v4-shims.min.css

v4-shims.min.css

62 ms

public.css

public.css

170 ms

jet-elements.css

jet-elements.css

79 ms

jet-elements-skin.css

jet-elements-skin.css

87 ms

elementor-icons.min.css

elementor-icons.min.css

101 ms

swiper.min.css

swiper.min.css

200 ms

frontend-lite.min.css

frontend-lite.min.css

127 ms

post-7.css

post-7.css

151 ms

post-98.css

post-98.css

253 ms

post-463.css

post-463.css

262 ms

further-space.min.css

further-space.min.css

171 ms

fontawesome.min.css

fontawesome.min.css

289 ms

solid.min.css

solid.min.css

280 ms

brands.min.css

brands.min.css

217 ms

jquery.min.js

jquery.min.js

578 ms

jquery-migrate.min.js

jquery-migrate.min.js

247 ms

js

js

65 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

282 ms

widget-icon-box.min.css

widget-icon-box.min.css

367 ms

post-716.css

post-716.css

372 ms

post-357.css

post-357.css

312 ms

hello-frontend.min.js

hello-frontend.min.js

308 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

402 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

336 ms

wp-polyfill.min.js

wp-polyfill.min.js

342 ms

hooks.min.js

hooks.min.js

367 ms

vue.min.js

vue.min.js

368 ms

jet-menu-public-scripts.js

jet-menu-public-scripts.js

499 ms

35 ms

fs-components.esm.js

fs-components.esm.js

482 ms

fs-components.js

fs-components.js

470 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

469 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

479 ms

webpack.runtime.min.js

webpack.runtime.min.js

464 ms

frontend-modules.min.js

frontend-modules.min.js

457 ms

p.css

p.css

24 ms

i18n.min.js

i18n.min.js

547 ms

frontend.min.js

frontend.min.js

559 ms

waypoints.min.js

waypoints.min.js

438 ms

core.min.js

core.min.js

412 ms

frontend.min.js

frontend.min.js

623 ms

elements-handlers.min.js

elements-handlers.min.js

424 ms

jet-elements.min.js

jet-elements.min.js

421 ms

widgets-scripts.js

widgets-scripts.js

482 ms

gtm.js

gtm.js

54 ms

analytics.js

analytics.js

133 ms

d

d

133 ms

d

d

133 ms

d

d

133 ms

BerlingskeSerif-Md.woff

BerlingskeSerif-Md.woff

266 ms

BerlingskeSerif-Blk.woff

BerlingskeSerif-Blk.woff

152 ms

js

js

138 ms

insight.min.js

insight.min.js

129 ms

events.js

events.js

175 ms

fbevents.js

fbevents.js

101 ms

fa-brands-400.woff

fa-brands-400.woff

185 ms

fa-brands-400.woff

fa-brands-400.woff

126 ms

d

d

53 ms

d

d

59 ms

d

d

92 ms

collect

collect

33 ms

collect

collect

59 ms

insight_tag_errors.gif

insight_tag_errors.gif

145 ms

ga-audiences

ga-audiences

32 ms

Accessibility Review

further.space accessibility score

95

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

further.space 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

further.space SEO score

100

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

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 Further.space 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 Further.space 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

further.space

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