Tools & Wizards About Us
wphistory.org screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wphistory.org

Winter Park History Museum — Collect. Preserve. Exhibit.

Page Load Speed

13.2 sec in total

First Response

4.1 sec

Resources Loaded

8.7 sec

Page Rendered

369 ms

wphistory.org screenshot

About Website

Click here to check amazing Wp History content. Otherwise, check out these important facts you probably never knew about wphistory.org

Located in the heart of Winter Park, this quaint museum tells the town's story through free educational exhibits, lecture series and outreach programs.

Visit wphistory.org

Key Findings

We analyzed Wphistory.org page load time and found that the first response time was 4.1 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wphistory.org performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.5 s

0/100

25%

SI (Speed Index)

Value22.8 s

0/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

wphistory.org

4146 ms

local-ga.js

215 ms

css

46 ms

sbi-styles.min.css

249 ms

style.min.css

294 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 67% of them (38 requests) were addressed to the original Wphistory.org, 18% (10 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Wphistory.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (43%)

Content Size

3.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wphistory.org main page is 3.1 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 208.6 kB

  • Original 237.8 kB
  • After minification 220.6 kB
  • After compression 29.1 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 208.6 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 67.5 kB

  • Original 1.4 MB
  • After minification 1.3 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. Wp History images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 709.5 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 362.2 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 709.5 kB or 66% of the original size.

CSS Optimization

-79%

Potential reduce by 360.5 kB

  • Original 456.9 kB
  • After minification 429.3 kB
  • After compression 96.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. Wphistory.org needs all CSS files to be minified and compressed as it can save up to 360.5 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wphistory.org

wphistory.org

4146 ms

local-ga.js

local-ga.js

215 ms

css

css

46 ms

sbi-styles.min.css

sbi-styles.min.css

249 ms

style.min.css

style.min.css

294 ms

oxygen.css

oxygen.css

178 ms

dashicons.min.css

dashicons.min.css

217 ms

reset.css

reset.css

204 ms

twentyeighteen.css

twentyeighteen.css

218 ms

jquery.min.js

jquery.min.js

255 ms

js

js

57 ms

css

css

63 ms

29.css

29.css

242 ms

356.css

356.css

254 ms

33.css

33.css

986 ms

9.css

9.css

254 ms

universal.css

universal.css

1023 ms

signup-form-widget.min.js

signup-form-widget.min.js

52 ms

css

css

31 ms

aos.css

aos.css

91 ms

rs6.css

rs6.css

150 ms

rbtools.min.js

rbtools.min.js

162 ms

rs6.min.js

rs6.min.js

296 ms

tracker.js

tracker.js

134 ms

aos.js

aos.js

135 ms

sbi-scripts.min.js

sbi-scripts.min.js

316 ms

dom-ready.min.js

dom-ready.min.js

166 ms

hooks.min.js

hooks.min.js

167 ms

i18n.min.js

i18n.min.js

184 ms

a11y.min.js

a11y.min.js

200 ms

mcjs.min.js

mcjs.min.js

202 ms

collect

collect

27 ms

js

js

76 ms

gtm.js

gtm.js

22 ms

dummy.png

dummy.png

91 ms

baseline-location_on-24px@2x.png

baseline-location_on-24px@2x.png

713 ms

baseline-access_time-24px@2x.png

baseline-access_time-24px@2x.png

719 ms

wphm_logo_white@2x.png

wphm_logo_white@2x.png

808 ms

sbi-sprite.png

sbi-sprite.png

63 ms

home_background@3x.png

home_background@3x.png

378 ms

wphistorymuseum.webp

wphistorymuseum.webp

277 ms

placeholder.png

placeholder.png

276 ms

winter-park-seal_white@2x.png

winter-park-seal_white@2x.png

277 ms

florida_arts_and_culture_logo_-_black_-_vertical-square.png

florida_arts_and_culture_logo_-_black_-_vertical-square.png

277 ms

ua_logo_footer.png

ua_logo_footer.png

329 ms

KtkuALODe433f0j1zMnFHdU.ttf

KtkuALODe433f0j1zMnFHdU.ttf

277 ms

KtkpALODe433f0j1zMF-OMWl42Q.ttf

KtkpALODe433f0j1zMF-OMWl42Q.ttf

329 ms

Banner-Final-e1712237299454.jpg

Banner-Final-e1712237299454.jpg

299 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

302 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf

301 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

301 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

301 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf

301 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf

301 ms

KtkrALODe433f0j1zMnAJWmn02P3Fw.ttf

KtkrALODe433f0j1zMnAJWmn02P3Fw.ttf

302 ms

KtkoALODe433f0j1zMnALdKCww.ttf

KtkoALODe433f0j1zMnALdKCww.ttf

345 ms

underscore-min.js

underscore-min.js

284 ms

Accessibility Review

wphistory.org accessibility score

91

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

Links do not have a discernible name

Best Practices

wphistory.org 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wphistory.org SEO score

83

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

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 Wphistory.org 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 Wphistory.org 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

wphistory.org

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