Tools & Wizards About Us
bodiehistory.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

bodiehistory.com

History of Bodie, California: Mining Ghost Town Comes Alive

Page Load Speed

214 ms in total

First Response

37 ms

Resources Loaded

104 ms

Page Rendered

73 ms

bodiehistory.com screenshot

About Website

Click here to check amazing Bodie History content. Otherwise, check out these important facts you probably never knew about bodiehistory.com

Bodie, California, a mining ghost town, is captured in Michael H. Piatt's thorougly researched history Bodie, 'The Mines are Looking Well', plus unpublished essays.

Visit bodiehistory.com

Key Findings

We analyzed Bodiehistory.com page load time and found that the first response time was 37 ms and then it took 177 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

bodiehistory.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

bodiehistory.com

37 ms

DM_redirect.js

9 ms

tracker.php

38 ms

boiler.jpg

35 ms

ga.js

6 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 76% of them (13 requests) were addressed to the original Bodiehistory.com, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Static.dudamobile.com. The less responsive or slowest element that took the longest time to load (38 ms) relates to the external source Stats.directnic.com.

Page Optimization Overview & Recommendations

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

Content Size

66.8 kB

After Optimization

57.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Bodiehistory.com main page is 66.8 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. 15% of websites need less resources to load. Images take 36.6 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 8.5 kB

  • Original 12.3 kB
  • After minification 11.4 kB
  • After compression 3.8 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 8.5 kB or 69% of the original size.

Image Optimization

-0%

Potential reduce by 98 B

  • Original 36.6 kB
  • After minification 36.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. Bodie History images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 283 B

  • Original 17.9 kB
  • After minification 17.9 kB
  • After compression 17.6 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

We found no issues to fix!

Requests Now

15

After Optimization

15

  • Images
  • JavaScript

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bodie History. According to our analytics all requests are already optimized.

Network Requests Diagram

bodiehistory.com

bodiehistory.com

37 ms

DM_redirect.js

DM_redirect.js

9 ms

tracker.php

tracker.php

38 ms

boiler.jpg

boiler.jpg

35 ms

ga.js

ga.js

6 ms

bodie-white.gif

bodie-white.gif

34 ms

myth-white.gif

myth-white.gif

34 ms

articles-white.gif

articles-white.gif

35 ms

book-white.gif

book-white.gif

35 ms

links-white.gif

links-white.gif

35 ms

main-st-599adb.jpg

main-st-599adb.jpg

34 ms

bodie-calif.gif

bodie-calif.gif

35 ms

history_and_research.gif

history_and_research.gif

35 ms

BODIE-1877-downtown.jpg

BODIE-1877-downtown.jpg

36 ms

datzmediawebcredit-small.jpg

datzmediawebcredit-small.jpg

36 ms

__utm.gif

__utm.gif

12 ms

wagon.jpg

wagon.jpg

11 ms

Accessibility Review

bodiehistory.com accessibility score

51

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

bodiehistory.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

bodiehistory.com SEO score

84

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bodiehistory.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 Bodiehistory.com main page’s claimed encoding is iso-8859-1. 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

bodiehistory.com

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