Tools & Wizards About Us
oldironpost.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

oldironpost.com

American Restaurant & Bar in Sherman, TX - Old Iron Post

Page Load Speed

1.8 sec in total

First Response

94 ms

Resources Loaded

1.5 sec

Page Rendered

199 ms

oldironpost.com screenshot

About Website

Visit oldironpost.com now to see the best up-to-date Old Iron Post content and also check out these interesting facts you probably never knew about oldironpost.com

We're an American restaurant & bar located in a beautifully restored building on the square of historic downtown Sherman, TX. Come see us...

Visit oldironpost.com

Key Findings

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

Performance Metrics

oldironpost.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

oldironpost.com

94 ms

www.oldironpost.com

651 ms

style.css

27 ms

classic-10_7.css

113 ms

style.min.css

49 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 79% of them (34 requests) were addressed to the original Oldironpost.com, 7% (3 requests) were made to Fonts.googleapis.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (651 ms) belongs to the original domain Oldironpost.com.

Page Optimization Overview & Recommendations

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

Content Size

583.6 kB

After Optimization

546.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oldironpost.com main page is 583.6 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. Images take 446.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.1 kB

  • Original 29.3 kB
  • After minification 29.3 kB
  • After compression 7.3 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 22.1 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 446.6 kB
  • After minification 442.0 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. Old Iron Post images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 3.2 kB

  • Original 70.2 kB
  • After minification 70.0 kB
  • After compression 67.0 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

-19%

Potential reduce by 7.1 kB

  • Original 37.5 kB
  • After minification 37.3 kB
  • After compression 30.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. Oldironpost.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 19% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oldironpost.com

oldironpost.com

94 ms

www.oldironpost.com

www.oldironpost.com

651 ms

style.css

style.css

27 ms

classic-10_7.css

classic-10_7.css

113 ms

style.min.css

style.min.css

49 ms

meanmenu.css

meanmenu.css

64 ms

superfish.css

superfish.css

64 ms

prettyPhoto.css

prettyPhoto.css

65 ms

default.css

default.css

67 ms

nivo-slider.css

nivo-slider.css

68 ms

1140.css

1140.css

71 ms

1140-responsive.css

1140-responsive.css

83 ms

css

css

30 ms

jquery.min.js

jquery.min.js

106 ms

jquery-migrate.min.js

jquery-migrate.min.js

85 ms

jquery.meanmenu.js

jquery.meanmenu.js

89 ms

jqsf.js

jqsf.js

91 ms

superfish.js

superfish.js

94 ms

window.load.js

window.load.js

103 ms

style.css

style.css

106 ms

social_media.css

social_media.css

111 ms

css

css

45 ms

css

css

50 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

114 ms

jquery.prettyPhoto.settings.js

jquery.prettyPhoto.settings.js

115 ms

comment-reply.min.js

comment-reply.min.js

124 ms

style.css

style.css

106 ms

style.css

style.css

25 ms

analytics.js

analytics.js

59 ms

warm-grain.jpg

warm-grain.jpg

49 ms

dark_leather.jpg

dark_leather.jpg

54 ms

old-iron-post-logo.png

old-iron-post-logo.png

70 ms

sideDivider.png

sideDivider.png

49 ms

sprites.png

sprites.png

49 ms

old-iron-post-building.jpg

old-iron-post-building.jpg

68 ms

chicken-tenders-150x150.png

chicken-tenders-150x150.png

98 ms

amazing-drinks.png

amazing-drinks.png

70 ms

shakedown-halloween-2015.png

shakedown-halloween-2015.png

91 ms

margaritas-300x300.png

margaritas-300x300.png

141 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

27 ms

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

u-4X0qWljRw-PfU81xCKCpdpbgZJl6XFpfEd7eA9BIxxkV2EH7alwg.ttf

34 ms

collect

collect

15 ms

js

js

70 ms

Accessibility Review

oldironpost.com accessibility score

70

Accessibility Issues

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

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

oldironpost.com SEO score

93

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

Image elements do not have [alt] attributes

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

oldironpost.com

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