6.4 sec in total
1.7 sec
4.2 sec
534 ms
Welcome to fegleyviolin.com homepage info - get ready to check Fegley Violin best content right away, or after learning these important things about fegleyviolin.com
Fegley String Instruments & Bows provides luthier services making fine handcrafted violins, violas, cellos, guitars and ukuleles. Serving clients with sting instruments and restoration services all th...
Visit fegleyviolin.comWe analyzed Fegleyviolin.com page load time and found that the first response time was 1.7 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fegleyviolin.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value10.5 s
0/100
25%
Value12.1 s
4/100
10%
Value620 ms
48/100
30%
Value0.033
100/100
15%
Value11.8 s
17/100
10%
1669 ms
106 ms
141 ms
107 ms
110 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 84% of them (98 requests) were addressed to the original Fegleyviolin.com, 13% (15 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Fegleyviolin.com.
Page size can be reduced by 125.4 kB (7%)
1.8 MB
1.6 MB
In fact, the total size of Fegleyviolin.com main page is 1.8 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. 80% 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 910.6 kB which makes up the majority of the site volume.
Potential reduce by 90.3 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 90.3 kB or 82% of the original size.
Potential reduce by 11.1 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. Fegley Violin images are well optimized though.
Potential reduce by 16.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.
Potential reduce by 7.4 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. Fegleyviolin.com has all CSS files already compressed.
Number of requests can be reduced by 83 (85%)
98
15
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fegley Violin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
fegleyviolin.com
1669 ms
frontend.css
106 ms
style.min.css
141 ms
styles.css
107 ms
style.css
110 ms
plugins.min.css
107 ms
modules.min.css
222 ms
font-awesome.min.css
153 ms
style.min.css
156 ms
ionicons.min.css
149 ms
style.css
176 ms
simple-line-icons.css
185 ms
dripicons.css
187 ms
icomoon.css
188 ms
blog.min.css
219 ms
mediaelementplayer-legacy.min.css
235 ms
wp-mediaelement.min.css
236 ms
modules-responsive.min.css
237 ms
blog-responsive.min.css
241 ms
style_dynamic_responsive.css
250 ms
style_dynamic.css
249 ms
js_composer.min.css
301 ms
css
38 ms
select2.css
255 ms
core-dashboard.min.css
269 ms
lightbox.min.css
273 ms
overrides.css
288 ms
jquery.min.js
288 ms
jquery-migrate.min.js
289 ms
jquery.blockUI.min.js
351 ms
add-to-cart.min.js
347 ms
js.cookie.min.js
349 ms
woocommerce.min.js
348 ms
woocommerce-add-to-cart.js
350 ms
css
45 ms
wc-blocks.css
189 ms
rs6.css
190 ms
hooks.min.js
192 ms
i18n.min.js
245 ms
index.js
246 ms
index.js
247 ms
rbtools.min.js
251 ms
rs6.min.js
310 ms
core.min.js
247 ms
tabs.min.js
248 ms
accordion.min.js
248 ms
mediaelement-and-player.min.js
307 ms
mediaelement-migrate.min.js
250 ms
wp-mediaelement.min.js
250 ms
jquery.appear.js
251 ms
js
149 ms
modernizr.js
295 ms
hoverIntent.min.js
271 ms
jquery.plugin.js
270 ms
jquery.countdown.min.js
268 ms
parallax.min.js
267 ms
select2.min.js
297 ms
easypiechart.js
294 ms
jquery.waypoints.min.js
285 ms
Chart.min.js
284 ms
counter.js
278 ms
fluidvids.min.js
266 ms
jquery.prettyPhoto.min.js
609 ms
jquery.nicescroll.min.js
596 ms
ScrollToPlugin.min.js
594 ms
TweenLite.min.js
594 ms
jquery.mixitup.min.js
533 ms
jquery.waitforimages.js
527 ms
jquery.easing.1.3.js
537 ms
skrollr.js
538 ms
bootstrapCarousel.js
522 ms
jquery.touchSwipe.min.js
518 ms
jquery.multiscroll.min.js
518 ms
typed.js
514 ms
slick.min.js
464 ms
isotope.pkgd.min.js
463 ms
modules.min.js
466 ms
blog.min.js
463 ms
js_composer_front.min.js
461 ms
like.js
461 ms
sourcebuster.min.js
461 ms
order-attribution.min.js
459 ms
jquery.touchwipe.min.js
461 ms
purify.min.js
459 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
82 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4uaVc.ttf
83 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
429 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
434 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
430 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
434 ms
panzoom.min.js
448 ms
KFOmCnqEu92Fr1Mu7GxP.ttf
433 ms
KFOlCnqEu92Fr1MmEU9fChc9.ttf
433 ms
KFOlCnqEu92Fr1MmSU5fChc9.ttf
432 ms
KFOkCnqEu92Fr1MmgVxGIzc.ttf
434 ms
KFOlCnqEu92Fr1MmWUlfChc9.ttf
436 ms
KFOlCnqEu92Fr1MmYUtfChc9.ttf
434 ms
jquery.lightbox.js
498 ms
fontawesome-webfont.woff
501 ms
ElegantIcons.woff
502 ms
Fegley-Violin-Shop-Reading-Pa.png
500 ms
Fegley-Violin-Shop-Reading-Pa-White.png
500 ms
dummy.png
499 ms
Fegley-New-Instruments-1.jpg
480 ms
Fegley-Restorations-1.jpg
471 ms
Fegley-Rental-Instruments-1.jpg
473 ms
Fegley-Violin-Restoration-Projects.jpg
473 ms
bridge-jpm-milene.jpg
471 ms
Spehlmann-Cello-2.jpg
471 ms
IMG_7286-800x600.jpeg
472 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
261 ms
webpic1-800x600.jpeg
124 ms
bridge-1-800x600.jpeg
200 ms
Fegley-Footer.jpg
200 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
80 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
80 ms
fegleyviolin.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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
fegleyviolin.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
fegleyviolin.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fegleyviolin.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 Fegleyviolin.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.
fegleyviolin.com
Open Graph data is detected on the main page of Fegley Violin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: