5 sec in total
1.3 sec
3.3 sec
474 ms
Click here to check amazing Yorkberg content for United States. Otherwise, check out these important facts you probably never knew about yorkberg.com
Visit yorkberg.comWe analyzed Yorkberg.com page load time and found that the first response time was 1.3 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
yorkberg.com performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value0.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
1307 ms
109 ms
126 ms
97 ms
86 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 73% of them (89 requests) were addressed to the original Yorkberg.com, 9% (11 requests) were made to Sumome-140a.kxcdn.com and 5% (6 requests) were made to Sumome.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Yorkberg.com.
Page size can be reduced by 3.1 MB (61%)
5.1 MB
2.0 MB
In fact, the total size of Yorkberg.com main page is 5.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. 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. CSS take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 55.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 55.3 kB or 79% of the original size.
Potential reduce by 92.8 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. Yorkberg images are well optimized though.
Potential reduce by 790.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 790.3 kB or 63% of the original size.
Potential reduce by 2.2 MB
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. Yorkberg.com needs all CSS files to be minified and compressed as it can save up to 2.2 MB or 91% of the original size.
Number of requests can be reduced by 82 (69%)
119
37
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yorkberg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 58 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
yorkberg.com
1307 ms
wp-emoji-release.min.js
109 ms
dashicons.min.css
126 ms
jquery-ui-dialog.min.css
97 ms
styles.css
86 ms
settings.css
93 ms
pac.css
100 ms
layout.css
127 ms
woocommerce-layout.css
172 ms
woocommerce.css
163 ms
colorbox.css
144 ms
prettyPhoto.css
172 ms
jquery.selectBox.css
225 ms
style.css
223 ms
font-awesome.min.css
245 ms
css
31 ms
font-awesome.min.css
241 ms
style.css
316 ms
prettyPhoto.css
236 ms
js_composer_front_custom.css
478 ms
woocommerce.css
277 ms
jquery.js
339 ms
jquery-migrate.min.js
283 ms
jquery.themepunch.tools.min.js
363 ms
jquery.themepunch.revolution.min.js
337 ms
add-to-cart.min.js
349 ms
woocommerce-add-to-cart.js
370 ms
bootstrap.min.js
358 ms
elevatezoom-min.js
405 ms
load.sumome.com
287 ms
E-v1.js
179 ms
isotope.min.css
448 ms
prettyPhoto.min.css
445 ms
core.min.js
415 ms
widget.min.js
433 ms
mouse.min.js
450 ms
resizable.min.js
461 ms
draggable.min.js
603 ms
button.min.js
604 ms
cfpop.js
52 ms
position.min.js
585 ms
dialog.min.js
530 ms
wpdialog.min.js
523 ms
jquery.form.min.js
522 ms
scripts.js
522 ms
jquery.blockUI.min.js
513 ms
woocommerce.min.js
496 ms
jquery.cookie.min.js
497 ms
cart-fragments.min.js
478 ms
woocompare.js
454 ms
jquery.colorbox-min.js
450 ms
jquery.prettyPhoto.min.js
450 ms
jquery.prettyPhoto.init.min.js
400 ms
jquery.selectBox.min.js
400 ms
jquery.yith-wcwl.js
460 ms
functions.js
376 ms
owl.carousel.js
453 ms
jquery.prettyPhoto.js
416 ms
suggest.min.js
415 ms
woocommerce.js
363 ms
wp-embed.min.js
361 ms
js_composer_front.min.js
362 ms
skrollr.min.js
351 ms
imagesloaded.pkgd.min.js
343 ms
isotope.pkgd.min.js
339 ms
jquery.prettyPhoto.min.js
330 ms
analytics.js
76 ms
logo.png
177 ms
header.jpg
410 ms
suitability.png
408 ms
socks-back.jpg
407 ms
image-11-1-500x645.jpg
408 ms
image-44-1-500x645.jpg
406 ms
wpspin_light.gif
405 ms
image-2-150x150.jpg
357 ms
sock-01.png
361 ms
image-0-150x150.jpg
355 ms
image-10-copy-150x150.jpg
356 ms
10.jpg
359 ms
09.jpg
357 ms
08.jpg
401 ms
06.jpg
404 ms
05.jpg
388 ms
04.jpg
401 ms
03.jpg
418 ms
02.jpg
438 ms
logo.png
448 ms
fontawesome-webfont.woff
482 ms
fontawesome-webfont.woff
451 ms
ec.js
18 ms
yorkberg.com
952 ms
yorkberg.com
965 ms
collect
34 ms
273 ms
ajax-loader.gif
134 ms
yt.jpg
185 ms
service.js
44 ms
service.js
43 ms
service.js
42 ms
service.js
41 ms
service.js
9 ms
load
219 ms
sumome-image-sharer.css
15 ms
sme-popup.css
14 ms
sumome-share-client.css
28 ms
css
43 ms
load
302 ms
load
313 ms
status
241 ms
status
278 ms
facebook-white-60.png
24 ms
shares.json
67 ms
links.getStats
67 ms
links.getStats
88 ms
count.json
62 ms
button_info.json
61 ms
yum-count
98 ms
pinterest-white-60.png
8 ms
sumome-white-60.png
6 ms
share
64 ms
rpc
93 ms
woocommerce-smallscreen.css
56 ms
yorkberg.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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
yorkberg.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
yorkberg.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yorkberg.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 Yorkberg.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.
yorkberg.com
Open Graph description is not detected on the main page of Yorkberg. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: