Tools & Wizards About Us
perthelhomes.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

perthelhomes.com

Perthel Homes – Building on three generations of quality

Page Load Speed

2 sec in total

First Response

162 ms

Resources Loaded

1.3 sec

Page Rendered

606 ms

perthelhomes.com screenshot

About Website

Welcome to perthelhomes.com homepage info - get ready to check Perthel Homes best content right away, or after learning these important things about perthelhomes.com

Visit perthelhomes.com

Key Findings

We analyzed Perthelhomes.com page load time and found that the first response time was 162 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

perthelhomes.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value2,040 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

perthelhomes.com

162 ms

perthelhomes.com

594 ms

magnific.css

12 ms

wp-matterport.css

15 ms

global.min.css

33 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 79% of them (64 requests) were addressed to the original Perthelhomes.com, 15% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (594 ms) belongs to the original domain Perthelhomes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 211.3 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Perthelhomes.com 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 982.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 104.0 kB

  • Original 128.4 kB
  • After minification 124.6 kB
  • After compression 24.5 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 104.0 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 15.5 kB

  • Original 982.0 kB
  • After minification 966.5 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. Perthel Homes images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 48.4 kB

  • Original 388.6 kB
  • After minification 388.6 kB
  • After compression 340.1 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 48.4 kB or 12% of the original size.

CSS Optimization

-23%

Potential reduce by 43.4 kB

  • Original 186.2 kB
  • After minification 185.4 kB
  • After compression 142.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. Perthelhomes.com needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 23% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

perthelhomes.com

perthelhomes.com

162 ms

perthelhomes.com

perthelhomes.com

594 ms

magnific.css

magnific.css

12 ms

wp-matterport.css

wp-matterport.css

15 ms

global.min.css

global.min.css

33 ms

header.min.css

header.min.css

32 ms

content.min.css

content.min.css

33 ms

footer.min.css

footer.min.css

26 ms

menu-addon.css

menu-addon.css

29 ms

frontend.min.css

frontend.min.css

26 ms

widget-image.min.css

widget-image.min.css

37 ms

widget-heading.min.css

widget-heading.min.css

36 ms

widget-icon-list.min.css

widget-icon-list.min.css

38 ms

widget-social-icons.min.css

widget-social-icons.min.css

36 ms

apple-webkit.min.css

apple-webkit.min.css

37 ms

widget-text-editor.min.css

widget-text-editor.min.css

35 ms

elementor-icons.min.css

elementor-icons.min.css

43 ms

swiper.min.css

swiper.min.css

41 ms

e-swiper.min.css

e-swiper.min.css

42 ms

post-10.css

post-10.css

41 ms

frontend.min.css

frontend.min.css

43 ms

uael-frontend.min.css

uael-frontend.min.css

44 ms

fadeInUp.min.css

fadeInUp.min.css

74 ms

widget-flip-box.min.css

widget-flip-box.min.css

75 ms

shapes.min.css

shapes.min.css

76 ms

widget-divider.min.css

widget-divider.min.css

75 ms

fluent-forms-public.css

fluent-forms-public.css

75 ms

fluentform-public-default.css

fluentform-public-default.css

72 ms

widget-carousel.min.css

widget-carousel.min.css

79 ms

fadeIn.min.css

fadeIn.min.css

81 ms

post-15.css

post-15.css

77 ms

post-145.css

post-145.css

77 ms

css

css

90 ms

fontawesome.min.css

fontawesome.min.css

81 ms

solid.min.css

solid.min.css

83 ms

regular.min.css

regular.min.css

84 ms

brands.min.css

brands.min.css

83 ms

jquery.min.js

jquery.min.js

86 ms

js

js

290 ms

css

css

117 ms

api.js

api.js

115 ms

fluent-forms-elementor-widget.css

fluent-forms-elementor-widget.css

82 ms

jquery-migrate.min.js

jquery-migrate.min.js

80 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

80 ms

magnific.min.js

magnific.min.js

62 ms

wp-matterport.js

wp-matterport.js

62 ms

navigation.min.js

navigation.min.js

63 ms

imagesloaded.min.js

imagesloaded.min.js

62 ms

form-submission.js

form-submission.js

60 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

59 ms

webpack.runtime.min.js

webpack.runtime.min.js

80 ms

frontend-modules.min.js

frontend-modules.min.js

80 ms

hooks.min.js

hooks.min.js

83 ms

i18n.min.js

i18n.min.js

79 ms

frontend.min.js

frontend.min.js

80 ms

core.min.js

core.min.js

80 ms

frontend.min.js

frontend.min.js

76 ms

elements-handlers.min.js

elements-handlers.min.js

76 ms

Ph_Logo_With_Tagline_White_RGB_1000px@144ppi.png

Ph_Logo_With_Tagline_White_RGB_1000px@144ppi.png

181 ms

Project-Showcase-1000px.jpg

Project-Showcase-1000px.jpg

25 ms

Design-Portfolio-1000px.jpg

Design-Portfolio-1000px.jpg

27 ms

Build-Your-Homes-1000px.jpg

Build-Your-Homes-1000px.jpg

26 ms

Home-Blueprint-Background.jpg

Home-Blueprint-Background.jpg

25 ms

Blue-Texture-Background.jpg

Blue-Texture-Background.jpg

28 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

76 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

88 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

118 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

135 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

135 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

135 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-jHgfY3lCA.ttf

136 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-lbgfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-lbgfY3lCA.ttf

136 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-n_gfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-n_gfY3lCA.ttf

137 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-gjgfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-gjgfY3lCA.ttf

138 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-uTnfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-uTnfY3lCA.ttf

137 ms

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

8vIU7ww63mVu7gtR-kwKxNvkNOjw-tbnfY3lCA.ttf

138 ms

eicons.woff

eicons.woff

133 ms

fa-solid-900.woff

fa-solid-900.woff

46 ms

fa-regular-400.woff

fa-regular-400.woff

73 ms

fa-brands-400.woff

fa-brands-400.woff

46 ms

recaptcha__en.js

recaptcha__en.js

128 ms

Accessibility Review

perthelhomes.com accessibility score

100

Accessibility Issues

Best Practices

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

perthelhomes.com 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 Perthelhomes.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 Perthelhomes.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

perthelhomes.com

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