3.2 sec in total
240 ms
2.8 sec
242 ms
Click here to check amazing Shore Fire content for United States. Otherwise, check out these important facts you probably never knew about shorefire.com
Creative communications for leaders in arts, culture, and entertainment
Visit shorefire.comWe analyzed Shorefire.com page load time and found that the first response time was 240 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
shorefire.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value26.2 s
0/100
25%
Value9.6 s
11/100
10%
Value1,380 ms
16/100
30%
Value0.18
67/100
15%
Value14.9 s
8/100
10%
240 ms
21 ms
119 ms
95 ms
11 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 47% of them (63 requests) were addressed to the original Shorefire.com, 26% (35 requests) were made to Static.xx.fbcdn.net and 4% (6 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Shorefire.com.
Page size can be reduced by 786.5 kB (15%)
5.4 MB
4.6 MB
In fact, the total size of Shorefire.com main page is 5.4 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 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 35.0 kB or 82% of the original size.
Potential reduce by 95.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. Shore Fire images are well optimized though.
Potential reduce by 380.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 380.5 kB or 67% of the original size.
Potential reduce by 275.8 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. Shorefire.com needs all CSS files to be minified and compressed as it can save up to 275.8 kB or 85% of the original size.
Number of requests can be reduced by 59 (46%)
127
68
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shore Fire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
shorefire.com
240 ms
css
21 ms
bootstrap.css
119 ms
app.css
95 ms
jquery-1.9.1.js
11 ms
jquery-ui.js
11 ms
bootstrap.min.js
69 ms
autocomplete
1488 ms
jquery.bxslider.js
213 ms
flipcard.js
50 ms
jquery.fancybox.min.js
215 ms
jquery.fancybox-thumbs.min.js
214 ms
jquery.fancybox-media.min.js
213 ms
jquery.fitvids.min.js
215 ms
retina.min.js
216 ms
app.js
215 ms
analytics.js
112 ms
fbds.js
109 ms
all.js
107 ms
embed.spotify.com
521 ms
logo.png
55 ms
social_sprite.png
55 ms
whyhunger-slide.jpg
79 ms
stvincent_1.jpg
148 ms
stlucia-slide_1.jpg
197 ms
comedy-dynamics-slide.jpg
147 ms
LDR-slide.jpg
180 ms
elviscostello.jpg
197 ms
iq2us.jpg
249 ms
marcus-roberts-slide.jpg
241 ms
emkinney_slide.jpg
283 ms
lee-brice-slide.jpg
337 ms
zbb-slide.jpg
314 ms
elipaperboy-slide.jpg
359 ms
AGrowth-Slide.jpg
321 ms
daddario-slide.jpg
415 ms
smithsonianfolkways.jpg
587 ms
a2im_logo_final_20090227_105152_1200_500_s_c1.jpg
592 ms
esperanza-slide.jpg
586 ms
tedtruckband-slide.jpg
587 ms
white-denim-slide.jpg
620 ms
maxwell.jpg
591 ms
ama.jpg
666 ms
capitoltheatre.jpg
768 ms
bonnier-slide.jpg
737 ms
brooklynbowl.jpg
826 ms
newbruce-slide.jpg
764 ms
glyphicons-halflings-regular.woff
737 ms
benharper-slide.jpg
888 ms
clv-slide.jpg
876 ms
Downtown-Music-P.jpg
832 ms
margoprice-slide.jpg
881 ms
errollgarner-slide.jpg
915 ms
leylamccalla-slide.jpg
971 ms
42 ms
collect
13 ms
upcoming_events_icon.png
887 ms
13 ms
Bruce_LA_square_400_400_s_c1.jpg
1000 ms
miesa-tbfy_remix_cover_400_400_s_c1.jpg
978 ms
xd_arbiter.php
18 ms
xd_arbiter.php
27 ms
collect
53 ms
TOLD_square.jpg
943 ms
featured_video_icon.png
834 ms
latest_press_release_icon.png
881 ms
dotted_line.png
849 ms
SF16-LOGO-01_RedSmile_BlackCopy.png
874 ms
MAIN_PRESS_SHOT_WD_250_250_s_c1.jpg
951 ms
Screen_Shot_2016-03-11_at_11.59.40_AM_250_250_s_c1.png
929 ms
Bonnie_Raitt_Color_headshot_credit_Marina_Chavez_1_250_250_s_c1.jpg
879 ms
Nonagon_Infinity_-_itunes_4000x4000_250_250_s_c1.jpg
865 ms
twitter_icon.png
802 ms
logo_sm.png
842 ms
spb.2ba359a.css
27 ms
analytics.js
72 ms
proxima_nova_regular_1.woff
168 ms
proxima_nova_thin_1.woff
169 ms
proxima_nova_semibold_1.woff
167 ms
spoticon_38d8b3d1a7647c3696de8982a0d8d7dd.svg
170 ms
md.2ba359a.js
37 ms
collect
132 ms
6059a565382ff0e24ea396e973fef8b8af964fd2
194 ms
all.js
63 ms
collect
35 ms
ga-audiences
57 ms
12 ms
xd_arbiter.php
5 ms
ping
16 ms
slider_controls.png
25 ms
print.css
150 ms
7 ms
like_box.php
298 ms
McLpmVM3wCm.css
36 ms
r6Aw0SZFbhw.css
38 ms
Czh0gDTFcBt.css
67 ms
hhn-1r1gAPt.css
56 ms
UwcJC8LA_KE.css
41 ms
X97l7PURgJ9.css
43 ms
BLxlHijS_qk.css
41 ms
VXtmSjXkO9S.css
63 ms
N5iHAgzP3Um.css
69 ms
OFG6f5m6ZIM.css
86 ms
FAHeNGXgPup.js
67 ms
FJmpeSpHpjS.js
118 ms
0wM5s1Khldu.js
63 ms
1bNoFZUdlYZ.js
65 ms
njO1TPvGzoR.js
130 ms
1QuX41zDRrx.js
131 ms
Oagsvfb4VWi.js
133 ms
m-2AbGY1fWh.js
139 ms
1FCa-btixu2.js
136 ms
IjqSyiwKeaX.js
136 ms
rBxSIHk4zIe.js
136 ms
pXuoz98hZ0k.js
167 ms
7BE0CZr3HTs.js
169 ms
pQrUxxo5oQp.js
169 ms
_UYztdBNTjs.js
168 ms
kvx5eeRG4FE.js
175 ms
Nn19HjwCsOL.js
174 ms
12744431_10156533637910503_1397529128173416852_n.png
160 ms
safe_image.php
149 ms
b8XhdWI9eAN.js
60 ms
safe_image.php
56 ms
1044639_10153036818580503_1810379121_n.png
55 ms
1930567_10156652253560503_6443677233380827645_n.jpg
61 ms
10626584_10156649008845503_8590234500866397803_n.jpg
58 ms
12719909_10156648696360503_996867930_n.jpg
62 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
51 ms
QDwYpIaRyfG.png
54 ms
l5aPruN9xMM.png
49 ms
K00K-UgnsKu.png
49 ms
K_65vAc89SX.png
59 ms
I6-MnjEovm5.js
4 ms
shorefire.com accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
shorefire.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
shorefire.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shorefire.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Shorefire.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.
shorefire.com
Open Graph data is detected on the main page of Shore Fire. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: