Tools & Wizards About Us
jwfranklin.com screenshot

Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

jwfranklin.com

FOR LEASE | J.W. FRANKLIN CO.

Page Load Speed

756 ms in total

First Response

43 ms

Resources Loaded

294 ms

Page Rendered

419 ms

jwfranklin.com screenshot

About Website

Visit jwfranklin.com now to see the best up-to-date Jw FRANKLIN content and also check out these interesting facts you probably never knew about jwfranklin.com

J.W. FRANKLIN CO. is a Broker, Owner & Developer of income producing properties, shopping centers, office buildings, & commercial sites in Missouri.

Visit jwfranklin.com

Key Findings

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

Performance Metrics

jwfranklin.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

jwfranklin.com

43 ms

www.jwfranklin.com

69 ms

481d11_9236d816846da371022bc91f04198ff9-321w.png

155 ms

jquery-3.7.0.min.js

30 ms

d-js-one-runtime-unified-desktop.min.js

41 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Jwfranklin.com, 46% (6 requests) were made to Lirp.cdn-website.com and 31% (4 requests) were made to Static.cdn-website.com. The less responsive or slowest element that took the longest time to load (155 ms) relates to the external source Lirp.cdn-website.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.4 kB (34%)

Content Size

444.3 kB

After Optimization

291.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Jwfranklin.com main page is 444.3 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. 35% of websites need less resources to load. Javascripts take 248.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 151.3 kB

  • Original 186.3 kB
  • After minification 182.2 kB
  • After compression 35.0 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 151.3 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 930 B

  • Original 9.4 kB
  • After minification 8.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. Jw FRANKLIN images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 109 B

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

Requests Breakdown

Number of requests can be reduced by 3 (30%)

Requests Now

10

After Optimization

7

  • Images
  • JavaScript

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

Network Requests Diagram

jwfranklin.com

jwfranklin.com

43 ms

www.jwfranklin.com

www.jwfranklin.com

69 ms

481d11_9236d816846da371022bc91f04198ff9-321w.png

481d11_9236d816846da371022bc91f04198ff9-321w.png

155 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

30 ms

d-js-one-runtime-unified-desktop.min.js

d-js-one-runtime-unified-desktop.min.js

41 ms

d-js-jquery-migrate.min.js

d-js-jquery-migrate.min.js

42 ms

runtime-react.js

runtime-react.js

46 ms

481d11_8f663c09aa6d459bbb9003037a7b6c14-mv2-1920w.jpg

481d11_8f663c09aa6d459bbb9003037a7b6c14-mv2-1920w.jpg

78 ms

481d11_b98c662f81e5499e912ffb1d3dafaead-mv2_d_2200_1700_s_2-1920w.jpg

481d11_b98c662f81e5499e912ffb1d3dafaead-mv2_d_2200_1700_s_2-1920w.jpg

82 ms

481d11_751f7fecd2234b4db053330beac48f13-mv2-1920w.jpg

481d11_751f7fecd2234b4db053330beac48f13-mv2-1920w.jpg

137 ms

northpark03-1920w.jpg

northpark03-1920w.jpg

134 ms

SFT_JPG-d702b894-1920w.jpg

SFT_JPG-d702b894-1920w.jpg

117 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5 ms

Accessibility Review

jwfranklin.com accessibility score

94

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

jwfranklin.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

jwfranklin.com SEO score

86

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

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 Jwfranklin.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 Jwfranklin.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

jwfranklin.com

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