1.4 sec in total
123 ms
1.2 sec
68 ms
Welcome to hornworld.com homepage info - get ready to check Hornworld best content right away, or after learning these important things about hornworld.com
French horn lessons. Glen Perry established Horn World in the 1990's to bring information and fun to the world of horn playing.
Visit hornworld.comWe analyzed Hornworld.com page load time and found that the first response time was 123 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
hornworld.com performance score
name
value
score
weighting
Value2.1 s
81/100
10%
Value3.0 s
78/100
25%
Value11.8 s
4/100
10%
Value3,520 ms
1/100
30%
Value0.047
99/100
15%
Value25.6 s
0/100
10%
123 ms
46 ms
27 ms
31 ms
66 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Hornworld.com, 93% (151 requests) were made to Static.parastorage.com and 3% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (238 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 694.0 kB (62%)
1.1 MB
420.8 kB
In fact, the total size of Hornworld.com main page is 1.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. 75% 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 62.6 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 62.6 kB or 81% of the original size.
Potential reduce by 630.9 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 630.9 kB or 62% of the original size.
Potential reduce by 557 B
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. Hornworld.com has all CSS files already compressed.
Number of requests can be reduced by 154 (97%)
159
5
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hornworld. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 150 to 1 for JavaScripts and as a result speed up the page load time.
hornworld.com
123 ms
www.hornworld.com
46 ms
require.min.js
27 ms
main-r.min.js
31 ms
bt
66 ms
UpgradeBrowser.js
28 ms
6c4b9b_d231fcd4e0f06dc51ca671fff9898943_201.json.z
238 ms
6c4b9b_5bfa35661348a9930e504928f22ea1a3_200.json.z
236 ms
ugc-viewer
22 ms
bt
20 ms
react-with-addons.min.js
19 ms
lodash.min.js
25 ms
wixCodeInit.min.js
21 ms
coreUtils.js
23 ms
coreUtils.min.js
43 ms
skins.min.js
81 ms
components.min.js
70 ms
core.min.js
79 ms
mobx.umd.min.js
78 ms
mobx-react.min.js
77 ms
TweenMax.min.js
80 ms
animations.min.js
81 ms
react-with-addons.min.js
191 ms
layout.min.js
191 ms
wixappsCore.min.js
191 ms
wixappsClassics.min.js
192 ms
container.min.js
191 ms
imageZoom.min.js
195 ms
mediaZoom.min.js
195 ms
imageZoomDisplayer.min.js
195 ms
matrixGallery.min.js
194 ms
slideShowGallery.min.js
194 ms
comboBoxInput.min.js
199 ms
dialogs.min.js
197 ms
table.min.js
198 ms
wixappsBuilder.min.js
197 ms
tpa.min.js
197 ms
dataFixer.min.js
196 ms
siteUtils.min.js
200 ms
image.min.js
198 ms
balata.min.js
202 ms
translationsUtils.min.js
201 ms
hammer.min.js
198 ms
utils.min.js
199 ms
fonts.min.js
202 ms
platformUtils-bundle.js
202 ms
loggingUtils.min.js
201 ms
imageClientApi.js
193 ms
swfobject.min.js
189 ms
santaProps.min.js
173 ms
displayer.min.js
167 ms
mousetrap.min.js
143 ms
DrawSVGPlugin.min.js
139 ms
react-dom.min.js
139 ms
ScrollToPlugin.min.js
136 ms
widgets.min.js
137 ms
react-dom-server.min.js
137 ms
imageCommon.min.js
182 ms
formCommon.min.js
182 ms
textCommon.min.js
183 ms
containerCommon.min.js
183 ms
socialCommon.min.js
182 ms
galleriesCommon.min.js
181 ms
buttonCommon.min.js
181 ms
compDesignUtils.min.js
182 ms
mediaCommon.min.js
182 ms
audioCommon.min.js
183 ms
skinExports.min.js
185 ms
compUtils.min.js
180 ms
mobileLayoutUtils.js
182 ms
pm-rpc.min.js
182 ms
tweenEngine.min.js
183 ms
multilingual.min.js
183 ms
render.min.js
183 ms
color.min.js
183 ms
zepto.min.js
183 ms
xss.min.js
184 ms
bluebird.min.js
185 ms
imageClientApi.min.js
182 ms
column.min.js
182 ms
siteBackground.min.js
183 ms
hoverBox.min.js
183 ms
mediaContainerFactory.min.js
182 ms
internalMarkings.min.js
182 ms
repeater.min.js
182 ms
zoomedImage.min.js
184 ms
menuButton.min.js
183 ms
a963d07260c2a6c5c39923d02fc52fb3_svgshape.v1.Ribbon.svg
179 ms
messageView.min.js
108 ms
backgroundCommon.min.js
69 ms
bt
109 ms
css
112 ms
TweenMax.min.js
14 ms
svgShape.min.js
13 ms
adminLoginButton.min.js
15 ms
wTwitterFollow.min.js
16 ms
facebookComments.min.js
16 ms
verticalAnchorsMenu.min.js
13 ms
facebookShare.min.js
15 ms
vKShareButton.min.js
17 ms
youTubeSubscribeButton.min.js
17 ms
itunesButton.min.js
19 ms
skypeCallButton.min.js
17 ms
fileUploader.min.js
19 ms
pinItPinWidget.min.js
18 ms
popupCloseTextButton.min.js
17 ms
radioButton.min.js
20 ms
radioGroup.min.js
21 ms
documentMedia.min.js
19 ms
datePicker.min.js
21 ms
contactForm.min.js
22 ms
subscribeForm.min.js
52 ms
textArea.min.js
21 ms
loginSocialBar.min.js
22 ms
googleMap.min.js
48 ms
soundCloudWidget.min.js
49 ms
paypalButton.min.js
56 ms
imageButton.min.js
50 ms
linkBar.min.js
54 ms
spotifyPlayer.min.js
51 ms
spotifyFollow.min.js
52 ms
twitterFeed.min.js
53 ms
backToTopButton.min.js
58 ms
svgCommon.min.js
54 ms
facebookLike.min.js
56 ms
facebookLikeBox.min.js
55 ms
flickrBadgeWidget.min.js
57 ms
rssButton.min.js
58 ms
tinyMenu.min.js
53 ms
groupContainer.min.js
54 ms
wGooglePlusOne.min.js
54 ms
pinterestPinIt.min.js
55 ms
pinterestFollow.min.js
54 ms
wTwitterTweet.min.js
55 ms
audioPlayer.min.js
70 ms
loginButton.min.js
70 ms
htmlComponent.min.js
70 ms
deadComponent.min.js
72 ms
mediaPlayer.min.js
69 ms
mediaControls.min.js
70 ms
singleAudioPlayer.min.js
71 ms
quickActionBar.min.js
70 ms
boxSlideShowSlide.min.js
70 ms
stripSlideShowSlide.min.js
70 ms
page.min.js
72 ms
bgImageStrip.min.js
70 ms
popupContainer.min.js
71 ms
stripContainer.min.js
71 ms
stripColumnsContainer.min.js
60 ms
exitMobileModeButton.min.js
44 ms
tpaGalleries.min.js
48 ms
flashComponent.min.js
45 ms
stripSlideShow.min.js
43 ms
mobileActionsMenu.min.js
45 ms
verticalMenu.min.js
44 ms
disqusComments.min.js
43 ms
checkbox.min.js
46 ms
gridComponent.min.js
46 ms
languageSelector.min.js
45 ms
lodash.min.js
25 ms
languages.css
43 ms
bt
8 ms
hornworld.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
hornworld.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hornworld.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hornworld.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 Hornworld.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.
hornworld.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: