46.5 sec in total
313 ms
44.1 sec
2.1 sec
Visit smithmusic.com now to see the best up-to-date Smith Music content and also check out these interesting facts you probably never knew about smithmusic.com
Providing Independent Music Distribution, Video Distribution, Royalty Collection, Catalog Management, and Publishing Administration Services.
Visit smithmusic.comWe analyzed Smithmusic.com page load time and found that the first response time was 313 ms and then it took 46.2 sec 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.
smithmusic.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value8.5 s
1/100
25%
Value7.9 s
23/100
10%
Value690 ms
43/100
30%
Value0
100/100
15%
Value9.7 s
29/100
10%
313 ms
563 ms
807 ms
625 ms
1519 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Smithmusic.com, 93% (150 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 (14.4 sec) relates to the external source Static.parastorage.com.
Page size can be reduced by 674.6 kB (62%)
1.1 MB
417.5 kB
In fact, the total size of Smithmusic.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. 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 58.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 58.6 kB or 80% of the original size.
Potential reduce by 615.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 615.5 kB or 61% 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. Smithmusic.com has all CSS files already compressed.
Number of requests can be reduced by 153 (96%)
159
6
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Smith Music. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 149 to 1 for JavaScripts and as a result speed up the page load time.
smithmusic.com
313 ms
www.smithmusic.com
563 ms
require.min.js
807 ms
main-r.min.js
625 ms
bt
1519 ms
5d9f68_03f4a25428d97ed951893c4c8baaf14d_415.json.z
1409 ms
5d9f68_b9617cdebda65fecd526994fcb239886_416.json.z
1415 ms
ugc-viewer
351 ms
bt
985 ms
react-with-addons.min.js
351 ms
lodash.min.js
823 ms
wixCodeInit.min.js
734 ms
coreUtils.js
731 ms
coreUtils.min.js
806 ms
skins.min.js
723 ms
components.min.js
598 ms
core.min.js
4711 ms
mobx.umd.min.js
4631 ms
mobx-react.min.js
4631 ms
TweenMax.min.js
6356 ms
animations.min.js
6356 ms
react-with-addons.min.js
6319 ms
layout.min.js
8805 ms
wixappsCore.min.js
8844 ms
wixappsClassics.min.js
8843 ms
container.min.js
8708 ms
imageZoom.min.js
8776 ms
mediaZoom.min.js
8975 ms
imageZoomDisplayer.min.js
8959 ms
matrixGallery.min.js
8975 ms
slideShowGallery.min.js
8919 ms
comboBoxInput.min.js
8975 ms
dialogs.min.js
8958 ms
table.min.js
9189 ms
wixappsBuilder.min.js
9188 ms
tpa.min.js
8951 ms
dataFixer.min.js
9124 ms
siteUtils.min.js
9095 ms
image.min.js
9125 ms
balata.min.js
9221 ms
translationsUtils.min.js
9222 ms
hammer.min.js
9185 ms
utils.min.js
9135 ms
fonts.min.js
9116 ms
platformUtils-bundle.js
9148 ms
loggingUtils.min.js
9227 ms
imageClientApi.js
9040 ms
swfobject.min.js
9011 ms
4f4fbf1f8b7146f69dafa4814a22e5f3.svg
5815 ms
santaProps.min.js
8928 ms
displayer.min.js
8951 ms
mousetrap.min.js
8828 ms
DrawSVGPlugin.min.js
8826 ms
react-dom.min.js
4871 ms
ScrollToPlugin.min.js
4870 ms
widgets.min.js
3183 ms
react-dom-server.min.js
3182 ms
imageCommon.min.js
3182 ms
formCommon.min.js
1088 ms
textCommon.min.js
1021 ms
containerCommon.min.js
1020 ms
socialCommon.min.js
967 ms
galleriesCommon.min.js
968 ms
buttonCommon.min.js
878 ms
compDesignUtils.min.js
916 ms
mediaCommon.min.js
839 ms
audioCommon.min.js
901 ms
skinExports.min.js
900 ms
compUtils.min.js
901 ms
mobileLayoutUtils.js
718 ms
pm-rpc.min.js
718 ms
tweenEngine.min.js
688 ms
multilingual.min.js
735 ms
render.min.js
734 ms
color.min.js
679 ms
zepto.min.js
674 ms
xss.min.js
672 ms
bluebird.min.js
672 ms
imageClientApi.min.js
672 ms
column.min.js
642 ms
siteBackground.min.js
641 ms
hoverBox.min.js
613 ms
mediaContainerFactory.min.js
585 ms
internalMarkings.min.js
586 ms
repeater.min.js
619 ms
zoomedImage.min.js
619 ms
menuButton.min.js
619 ms
messageView.min.js
14404 ms
backgroundCommon.min.js
12211 ms
bt
6513 ms
css
3671 ms
TweenMax.min.js
3622 ms
svgShape.min.js
2404 ms
adminLoginButton.min.js
2402 ms
wTwitterFollow.min.js
2474 ms
facebookComments.min.js
2565 ms
verticalAnchorsMenu.min.js
2507 ms
facebookShare.min.js
2462 ms
vKShareButton.min.js
2569 ms
youTubeSubscribeButton.min.js
2538 ms
itunesButton.min.js
2858 ms
skypeCallButton.min.js
2922 ms
fileUploader.min.js
2890 ms
pinItPinWidget.min.js
2889 ms
popupCloseTextButton.min.js
2920 ms
radioButton.min.js
2765 ms
radioGroup.min.js
2878 ms
documentMedia.min.js
2856 ms
datePicker.min.js
2855 ms
contactForm.min.js
2856 ms
subscribeForm.min.js
2856 ms
textArea.min.js
2876 ms
loginSocialBar.min.js
2978 ms
googleMap.min.js
2978 ms
soundCloudWidget.min.js
2938 ms
paypalButton.min.js
2906 ms
imageButton.min.js
2937 ms
linkBar.min.js
2936 ms
spotifyPlayer.min.js
3477 ms
spotifyFollow.min.js
3292 ms
twitterFeed.min.js
3477 ms
backToTopButton.min.js
3291 ms
svgCommon.min.js
3497 ms
facebookLike.min.js
3252 ms
facebookLikeBox.min.js
3437 ms
flickrBadgeWidget.min.js
3436 ms
rssButton.min.js
3436 ms
tinyMenu.min.js
3446 ms
groupContainer.min.js
3376 ms
wGooglePlusOne.min.js
3329 ms
pinterestPinIt.min.js
3306 ms
pinterestFollow.min.js
3286 ms
wTwitterTweet.min.js
3286 ms
audioPlayer.min.js
3225 ms
loginButton.min.js
3321 ms
htmlComponent.min.js
3033 ms
deadComponent.min.js
3032 ms
mediaPlayer.min.js
3002 ms
mediaControls.min.js
3001 ms
singleAudioPlayer.min.js
2971 ms
quickActionBar.min.js
2971 ms
boxSlideShowSlide.min.js
2943 ms
stripSlideShowSlide.min.js
3044 ms
page.min.js
3026 ms
bgImageStrip.min.js
3042 ms
popupContainer.min.js
3024 ms
stripContainer.min.js
3023 ms
stripColumnsContainer.min.js
3008 ms
exitMobileModeButton.min.js
2977 ms
tpaGalleries.min.js
2978 ms
flashComponent.min.js
2977 ms
stripSlideShow.min.js
2939 ms
mobileActionsMenu.min.js
2726 ms
verticalMenu.min.js
2662 ms
disqusComments.min.js
2625 ms
checkbox.min.js
2624 ms
gridComponent.min.js
2497 ms
languageSelector.min.js
2497 ms
lodash.min.js
2191 ms
bt
125 ms
languages.css
3193 ms
smithmusic.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
smithmusic.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
smithmusic.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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smithmusic.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 Smithmusic.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.
smithmusic.com
Open Graph data is detected on the main page of Smith Music. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: