5.7 sec in total
133 ms
5.4 sec
238 ms
Welcome to bodie.com homepage info - get ready to check Bodie best content for United States right away, or after learning these important things about bodie.com
Bodie - a town frozen in time in a “state of arrested decay”. Explore Bodie.com to learn more. Bodie is an original mining town from the late 1800’s.
Visit bodie.comWe analyzed Bodie.com page load time and found that the first response time was 133 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
bodie.com performance score
name
value
score
weighting
Value11.5 s
0/100
10%
Value26.4 s
0/100
25%
Value14.7 s
1/100
10%
Value3,160 ms
2/100
30%
Value0.148
76/100
15%
Value26.1 s
0/100
10%
133 ms
310 ms
78 ms
185 ms
244 ms
Our browser made a total of 188 requests to load all elements on the main page. We found that 60% of them (113 requests) were addressed to the original Bodie.com, 12% (22 requests) were made to Gstatic.com and 8% (15 requests) were made to Cdn.datatables.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Bodie.com.
Page size can be reduced by 207.2 kB (8%)
2.6 MB
2.4 MB
In fact, the total size of Bodie.com main page is 2.6 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 151.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 151.8 kB or 80% of the original size.
Potential reduce by 7.2 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 images are well optimized though.
Potential reduce by 36.3 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.
Potential reduce by 12.0 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. Bodie.com has all CSS files already compressed.
Number of requests can be reduced by 152 (86%)
177
25
The browser has sent 177 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bodie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 106 to 1 for JavaScripts and from 48 to 1 for CSS and as a result speed up the page load time.
bodie.com
133 ms
www.bodie.com
310 ms
colorbox.css
78 ms
imgmap_style.css
185 ms
style.min.css
244 ms
cws-google-picasa-pro-public.css
194 ms
lightbox.css
190 ms
dashicons.min.css
247 ms
font-awesome.min.css
190 ms
css
77 ms
etlak-frontend.css
236 ms
etlak-responsive.css
248 ms
jquery.dataTables.min.css
87 ms
buttons.dataTables.min.css
100 ms
select.dataTables.min.css
99 ms
fixedHeader.dataTables.min.css
93 ms
fixedColumns.dataTables.min.css
102 ms
responsive.dataTables.min.css
92 ms
style.css
245 ms
ftpair-mypuzzle.css
243 ms
sliding-plugin.css
286 ms
default.css
291 ms
datatables-row-details.min.css
291 ms
twenty20.css
291 ms
buttons.min.css
292 ms
mediaelementplayer-legacy.min.css
293 ms
wp-mediaelement.min.css
337 ms
media-views.min.css
342 ms
imgareaselect.css
345 ms
admin.css
346 ms
fontfaces.css
346 ms
style.css
347 ms
css
89 ms
style.css
389 ms
app.css
393 ms
tablepress-responsive.min.css
393 ms
style.css
394 ms
splide.min.css
396 ms
baguettebox.min.css
398 ms
photonic.min.css
440 ms
ytprefs.min.css
444 ms
jquery.min.js
500 ms
jquery-migrate.min.js
449 ms
jquery.colorbox-min.js
449 ms
jquery.dataTables.min.js
98 ms
dataTables.buttons.min.js
97 ms
buttons.colVis.min.js
96 ms
buttons.print.min.js
104 ms
pdfmake.min.js
131 ms
vfs_fonts.js
173 ms
jszip.min.js
155 ms
buttons.html5.min.js
106 ms
dataTables.select.min.js
104 ms
dataTables.fixedHeader.min.js
110 ms
dataTables.fixedColumns.min.js
112 ms
dataTables.responsive.min.js
111 ms
jsapi
73 ms
sdk.js
65 ms
js
107 ms
info
107 ms
counter.js
129 ms
element.js
90 ms
api.js
93 ms
shortcodes.css
444 ms
utils.min.js
428 ms
loader.js
24 ms
jquery.imagemapster.min.js
378 ms
imagemapper_script.js
346 ms
DOMPurify.min.js
338 ms
cws-google-picasa-pro-public.js
342 ms
et-frontend-script.js
365 ms
igsv-datatables.js
2256 ms
igsv-gvizcharts.js
2257 ms
general.js
2258 ms
ftpair-mypuzzle.js
2258 ms
sliding_plugin.js
2257 ms
jquery.bpopup-0.7.0.min.js
2258 ms
svgs-inline-min.js
2218 ms
moxie.min.js
2215 ms
plupload.min.js
2212 ms
wp-hide-post-public.js
2222 ms
jquery.mobile.custom.min.js
2220 ms
slider.js
2223 ms
ytprefs.min.js
2183 ms
core.min.js
2178 ms
mouse.min.js
2178 ms
resizable.min.js
2178 ms
draggable.min.js
2177 ms
controlgroup.min.js
2174 ms
checkboxradio.min.js
2137 ms
button.min.js
2132 ms
dialog.min.js
2132 ms
editor.min.js
2129 ms
clicker.js
2129 ms
jquery.twenty20.js
2129 ms
jquery.event.move.js
2086 ms
underscore.min.js
2080 ms
shortcode.min.js
2079 ms
backbone.min.js
2079 ms
wp-util.min.js
2078 ms
wp-backbone.min.js
2036 ms
media-models.min.js
2033 ms
wp-plupload.min.js
2014 ms
sortable.min.js
2009 ms
mediaelement-and-player.min.js
2009 ms
mediaelement-migrate.min.js
2009 ms
wp-mediaelement.min.js
65 ms
loader.js
44 ms
api-request.min.js
97 ms
wp-polyfill-inert.min.js
96 ms
regenerator-runtime.min.js
95 ms
wp-polyfill.min.js
95 ms
dom-ready.min.js
94 ms
hooks.min.js
95 ms
i18n.min.js
150 ms
a11y.min.js
140 ms
clipboard.min.js
139 ms
media-views.min.js
138 ms
media-editor.min.js
135 ms
s5.gif
76 ms
media-audiovideo.min.js
140 ms
media_button.js
141 ms
fitvids.min.js
140 ms
frontend.js
142 ms
imagesloaded.min.js
209 ms
masonry.min.js
210 ms
jquery.masonry.min.js
268 ms
close.png
267 ms
loading.gif
267 ms
prev.png
267 ms
next.png
266 ms
Untitled-6.png
266 ms
header101.jpg
535 ms
Header31.jpg
534 ms
header71.jpg
534 ms
header51.jpg
532 ms
nugget.gif
387 ms
sdk.js
43 ms
booked-wzs-widget-160x275.css
56 ms
mp-background-tile.jpg
472 ms
js
55 ms
analytics.js
176 ms
tooltip.css
32 ms
util.css
40 ms
controls.css
110 ms
table.css
111 ms
format.css
111 ms
annotationchart.css
112 ms
jsapi_compiled_default_module.js
126 ms
jsapi_compiled_graphics_module.js
109 ms
jsapi_compiled_ui_module.js
173 ms
jsapi_compiled_corechart_module.js
169 ms
jsapi_compiled_controls_module.js
170 ms
jsapi_compiled_table_module.js
169 ms
jsapi_compiled_annotationchart_module.js
168 ms
jsapi_compiled_annotatedtimeline_module.js
170 ms
jsapi_compiled_gauge_module.js
173 ms
jsapi_compiled_geo_module.js
172 ms
jsapi_compiled_geochart_module.js
172 ms
jsapi_compiled_fw_module.js
172 ms
dygraph-tickers-combined.js
310 ms
jsapi_compiled_timeline_module.js
309 ms
u-440qyriQwlOrhSvowK_l5-fCZK.woff
168 ms
u-4n0qyriQwlOrhSvowK_l521wRZWMf8.woff
308 ms
u-4n0qyriQwlOrhSvowK_l52xwNZWMf8.woff
367 ms
u-4n0qyriQwlOrhSvowK_l52_wFZWMf8.woff
366 ms
icomoon.woff
438 ms
Ad-729x90-8bit.png
466 ms
Ad-300x250-8bit.png
464 ms
wbig.png
384 ms
IOyu6jI_Zg0
376 ms
SocialShareImage-Museum1.jpg
799 ms
wsmall.png
375 ms
serioussliderglyphs.ttf
325 ms
t.php
359 ms
collect
144 ms
collect
150 ms
iframe_api
127 ms
www-player.css
25 ms
www-embed-player.js
23 ms
base.js
72 ms
www-widgetapi.js
50 ms
ad_status.js
247 ms
YjCNJ0mFj9HiCkQt39lQVpZzkP0G8dlYH-ABayRLdFs.js
131 ms
embed.js
84 ms
id
120 ms
KFOmCnqEu92Fr1Mu4mxM.woff
21 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
21 ms
bodie.com accessibility score
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
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
bodie.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
bodie.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bodie.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 Bodie.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.
bodie.com
Open Graph data is detected on the main page of Bodie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: