Tools & Wizards About Us
tpestate.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tpestate.com

TpESTATE - Sustainable Real Estate Developer - Eco-Friendly Builder - Sierra Leone

Page Load Speed

3.3 sec in total

First Response

165 ms

Resources Loaded

2.6 sec

Page Rendered

590 ms

tpestate.com screenshot

About Website

Visit tpestate.com now to see the best up-to-date TpESTATE content for United States and also check out these interesting facts you probably never knew about tpestate.com

Sustainable real estate property development and builder in Sierra Leone. We architect, design, 3D Model, render and build eco-friendly homes

Visit tpestate.com

Key Findings

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

Performance Metrics

tpestate.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

tpestate.sl

165 ms

mediaelementplayer-legacy.min.css

54 ms

wp-mediaelement.min.css

62 ms

extendify-utilities.css

179 ms

all-css.css

129 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Tpestate.com, 28% (22 requests) were made to C0.wp.com and 14% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.9 kB (6%)

Content Size

2.4 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tpestate.com main page is 2.4 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 135.2 kB

  • Original 163.1 kB
  • After minification 156.4 kB
  • After compression 27.9 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 135.2 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.0 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. TpESTATE images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 374.9 kB
  • After minification 374.9 kB
  • After compression 372.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 1.5 kB

  • Original 150.4 kB
  • After minification 149.8 kB
  • After compression 148.9 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. Tpestate.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 53 (80%)

Requests Now

66

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tpestate.sl

tpestate.sl

165 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

54 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

62 ms

extendify-utilities.css

extendify-utilities.css

179 ms

all-css.css

all-css.css

129 ms

all.min.css

all.min.css

125 ms

style.css

style.css

128 ms

frontend-lite.min.css

frontend-lite.min.css

149 ms

swiper.min.css

swiper.min.css

153 ms

post-3.css

post-3.css

219 ms

frontend-lite.min.css

frontend-lite.min.css

472 ms

post-2964.css

post-2964.css

245 ms

css

css

75 ms

jetpack.css

jetpack.css

59 ms

jquery.min.js

jquery.min.js

64 ms

jquery-migrate.min.js

jquery-migrate.min.js

63 ms

frontend.js

frontend.js

236 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

63 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

64 ms

wp-polyfill.min.js

wp-polyfill.min.js

66 ms

hooks.min.js

hooks.min.js

64 ms

i18n.min.js

i18n.min.js

65 ms

i18n-loader.js

i18n-loader.js

255 ms

react.min.js

react.min.js

66 ms

react-dom.min.js

react-dom.min.js

69 ms

escape-html.min.js

escape-html.min.js

66 ms

element.min.js

element.min.js

66 ms

chatbot.js

chatbot.js

393 ms

highlight.min.js

highlight.min.js

341 ms

js

js

104 ms

widget-icon-list.min.css

widget-icon-list.min.css

330 ms

animations.min.css

animations.min.css

368 ms

image-cdn.js

image-cdn.js

430 ms

url.min.js

url.min.js

65 ms

jp-search.js

jp-search.js

439 ms

w.js

w.js

62 ms

all-scripts.js

all-scripts.js

894 ms

houzez-instant-page.js

houzez-instant-page.js

478 ms

core.min.js

core.min.js

66 ms

menu.min.js

menu.min.js

64 ms

dom-ready.min.js

dom-ready.min.js

66 ms

a11y.min.js

a11y.min.js

65 ms

autocomplete.min.js

autocomplete.min.js

67 ms

mouse.min.js

mouse.min.js

67 ms

slider.min.js

slider.min.js

66 ms

custom.min.js

custom.min.js

500 ms

e-202410.js

e-202410.js

61 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

518 ms

webpack.runtime.min.js

webpack.runtime.min.js

529 ms

frontend-modules.min.js

frontend-modules.min.js

577 ms

frontend.min.js

frontend.min.js

611 ms

waypoints.min.js

waypoints.min.js

613 ms

frontend.min.js

frontend.min.js

617 ms

elements-handlers.min.js

elements-handlers.min.js

631 ms

css

css

15 ms

style.css

style.css

562 ms

tpestate-aframe-designs-thatched-roof-3.jpg

tpestate-aframe-designs-thatched-roof-3.jpg

1643 ms

logo-white.png

logo-white.png

462 ms

logo.png

logo.png

126 ms

lazyloader-1.gif

lazyloader-1.gif

462 ms

Google__G__Logo.svg

Google__G__Logo.svg

493 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjZ-Ek-_0ew.ttf

433 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjZ-Ek-_0ew.ttf

524 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfAZ9hjZ-Ek-_0ew.ttf

522 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyfAZ9hjZ-Ek-_0ew.ttf

503 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyeAZ9hjZ-Ek-_0ew.ttf

522 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjZ-Ek-_0ew.ttf

576 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjZ-Ek-_0ew.ttf

520 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuDyYAZ9hjZ-Ek-_0ew.ttf

576 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjZ-Ek-_0ew.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYAZ9hjZ-Ek-_0ew.ttf

576 ms

92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI0un_HKCEk.ttf

92zPtBhPNqw79Ij1E865zBUv7myRJTVBNI0un_HKCEk.ttf

576 ms

92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI0un_HKCEk.ttf

92zPtBhPNqw79Ij1E865zBUv7myjJTVBNI0un_HKCEk.ttf

576 ms

houzez-iconfont.ttf

houzez-iconfont.ttf

340 ms

g.gif

g.gif

367 ms

g.gif

g.gif

76 ms

prev.png

prev.png

143 ms

next.png

next.png

143 ms

loading.gif

loading.gif

145 ms

close.png

close.png

146 ms

Accessibility Review

tpestate.com accessibility score

83

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

Buttons do not have an accessible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tpestate.com SEO score

93

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

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

tpestate.com

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