Tools & Wizards About Us
historicdowntownpm.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

historicdowntownpm.com

Historic Downtown PM: Residential & Commercial Property Management Company

Page Load Speed

1.3 sec in total

First Response

37 ms

Resources Loaded

661 ms

Page Rendered

563 ms

historicdowntownpm.com screenshot

About Website

Click here to check amazing Historic Downtown PM content. Otherwise, check out these important facts you probably never knew about historicdowntownpm.com

Contact our property management team about our residential and commercial real estate properties. We'll help with rental applications and provide information on available homes and offices for re...

Visit historicdowntownpm.com

Key Findings

We analyzed Historicdowntownpm.com page load time and found that the first response time was 37 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

historicdowntownpm.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

historicdowntownpm.com

37 ms

historicdowntownpm.com

149 ms

analytics.js

69 ms

style.css

54 ms

style.min.css

63 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original Historicdowntownpm.com, 54% (34 requests) were made to S19571.pcdn.co and 8% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (198 ms) relates to the external source Cdn.userway.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.0 kB (2%)

Content Size

2.3 MB

After Optimization

2.3 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Historicdowntownpm.com main page is 2.3 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. Only a small number of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-2%

Potential reduce by 44.1 kB

  • Original 2.0 MB
  • After minification 1.9 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. Historic Downtown PM images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.7 kB

  • Original 364.1 kB
  • After minification 364.1 kB
  • After compression 362.4 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

-6%

Potential reduce by 2.2 kB

  • Original 33.6 kB
  • After minification 33.6 kB
  • After compression 31.4 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. Historicdowntownpm.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (74%)

Requests Now

50

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historicdowntownpm.com

historicdowntownpm.com

37 ms

historicdowntownpm.com

historicdowntownpm.com

149 ms

analytics.js

analytics.js

69 ms

style.css

style.css

54 ms

style.min.css

style.min.css

63 ms

styles.css

styles.css

53 ms

pagenavi-css.css

pagenavi-css.css

57 ms

dashicons.min.css

dashicons.min.css

61 ms

css

css

90 ms

bootstrap.min.css

bootstrap.min.css

56 ms

font-awesome.css

font-awesome.css

66 ms

flexslider.css

flexslider.css

67 ms

fancybox.min.css

fancybox.min.css

68 ms

custom.css

custom.css

69 ms

ipad.css

ipad.css

68 ms

mobile.css

mobile.css

71 ms

jquery.min.js

jquery.min.js

71 ms

jquery-migrate.min.js

jquery-migrate.min.js

69 ms

responsive-menu.js

responsive-menu.js

72 ms

bootstrap.min.js

bootstrap.min.js

73 ms

jquery.flexslider.js

jquery.flexslider.js

72 ms

fancybox.min.js

fancybox.min.js

72 ms

custom.js

custom.js

71 ms

parallax.js

parallax.js

73 ms

js

js

135 ms

hooks.min.js

hooks.min.js

72 ms

i18n.min.js

i18n.min.js

73 ms

index.js

index.js

73 ms

index.js

index.js

74 ms

api.js

api.js

126 ms

wp-polyfill.min.js

wp-polyfill.min.js

74 ms

index.js

index.js

72 ms

collect

collect

88 ms

Housing-Badge.webp

Housing-Badge.webp

28 ms

hdp-home-banner.jpg

hdp-home-banner.jpg

27 ms

001_LH_7_3_19.jpg

001_LH_7_3_19.jpg

86 ms

widget.js

widget.js

198 ms

99%20Sussex%20Exterior%201.jpg

99%20Sussex%20Exterior%201.jpg

178 ms

89%20Wayne%20street%20facade.jpg

89%20Wayne%20street%20facade.jpg

174 ms

slider-form-bg.png

slider-form-bg.png

35 ms

title-bg.png

title-bg.png

35 ms

image.png

image.png

34 ms

logo-1.png

logo-1.png

35 ms

footer-logo-1.webp

footer-logo-1.webp

47 ms

recaptcha__en.js

recaptcha__en.js

82 ms

Lato-Bold.woff

Lato-Bold.woff

53 ms

opensans-regular-webfont.woff

opensans-regular-webfont.woff

14 ms

js

js

125 ms

anchor

anchor

43 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

17 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

29 ms

opensans-italic-webfont.woff

opensans-italic-webfont.woff

17 ms

opensans-bold-webfont.woff

opensans-bold-webfont.woff

15 ms

widget_app_base_1725874918757.js

widget_app_base_1725874918757.js

19 ms

styles__ltr.css

styles__ltr.css

5 ms

recaptcha__en.js

recaptcha__en.js

15 ms

K1x6b-2KMXAL0IlzeahUAOCVah6M7Udib3NOSV9xjhQ.js

K1x6b-2KMXAL0IlzeahUAOCVah6M7Udib3NOSV9xjhQ.js

31 ms

webworker.js

webworker.js

30 ms

logo_48.png

logo_48.png

21 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

33 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

43 ms

recaptcha__en.js

recaptcha__en.js

39 ms

Accessibility Review

historicdowntownpm.com accessibility score

87

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

historicdowntownpm.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

historicdowntownpm.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Historicdowntownpm.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Historicdowntownpm.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

historicdowntownpm.com

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