5.1 sec in total
817 ms
3.8 sec
402 ms
Click here to check amazing Sherlock Holmes content. Otherwise, check out these important facts you probably never knew about sherlockholmes.com
Visit sherlockholmes.comWe analyzed Sherlockholmes.com page load time and found that the first response time was 817 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sherlockholmes.com performance score
name
value
score
weighting
Value2.0 s
84/100
10%
Value2.0 s
97/100
25%
Value5.8 s
49/100
10%
Value30 ms
100/100
30%
Value0.179
67/100
15%
Value4.2 s
86/100
10%
817 ms
24 ms
282 ms
285 ms
287 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 95% of them (93 requests) were addressed to the original Sherlockholmes.com, 4% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) 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 Sherlockholmes.com.
Page size can be reduced by 555.3 kB (25%)
2.2 MB
1.7 MB
In fact, the total size of Sherlockholmes.com main page is 2.2 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.6 kB or 80% of the original size.
Potential reduce by 26.5 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. Sherlock Holmes images are well optimized though.
Potential reduce by 412.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 412.5 kB or 69% of the original size.
Potential reduce by 89.7 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. Sherlockholmes.com needs all CSS files to be minified and compressed as it can save up to 89.7 kB or 83% of the original size.
Number of requests can be reduced by 69 (75%)
92
23
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sherlock Holmes. 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 15 to 1 for CSS and as a result speed up the page load time.
sherlockholmes.com
817 ms
css
24 ms
loader.css
282 ms
reset.css
285 ms
grid.css
287 ms
icons.css
429 ms
style.css
570 ms
shortcodes.css
295 ms
ruby-red.css
424 ms
animations.css
427 ms
ie.css
430 ms
common.css
442 ms
skin.css
568 ms
custom.css
574 ms
style.css
577 ms
styles.css
575 ms
jquery.js
1177 ms
jquery-migrate.min.js
709 ms
selectivizr-min.js
709 ms
comment-reply.min.js
713 ms
boot.js
713 ms
jquery.mobile.custom.min.js
853 ms
jquery.pixelentity.lazyload.js
851 ms
jquery.theme.utils.js
852 ms
jquery.mousewheel.js
853 ms
jquery.pixelentity.utils.browser.js
854 ms
jquery.pixelentity.utils.geom.js
994 ms
jquery.pixelentity.utils.preloader.js
995 ms
jquery.pixelentity.utils.transition.js
998 ms
jquery.pixelentity.transform.js
997 ms
jquery.pixelentity.utils.youtube.js
998 ms
froogaloop.js
1137 ms
jquery.pixelentity.utils.vimeo.js
1138 ms
jquery.pixelentity.video.js
1142 ms
jquery.pixelentity.videoPlayer.js
1140 ms
jquery.pixelentity.utils.ticker.js
1141 ms
jquery.pixelentity.backgroundSlider.js
1279 ms
jquery.pixelentity.flare.lightbox.js
1292 ms
jquery.pixelentity.simplethumb.js
1010 ms
jquery.pixelentity.flare.lightbox.render.gallery.js
1007 ms
jquery.pixelentity.flare.lightbox.render.image.js
1006 ms
smoothscroll.js
1033 ms
vegas.js
1007 ms
jquery.imagesloaded.js
1005 ms
jquery.mixitup.js
1148 ms
jquery.countto.js
1005 ms
wp-emoji-release.min.js
1033 ms
jqueryui.js
1003 ms
video.js
1142 ms
bigvideo.js
1008 ms
waypoints.js
1004 ms
parallax.js
1045 ms
jquery.pixelentity.contactForm.js
1014 ms
jquery.pixelentity.widgets.js
1014 ms
jquery.pixelentity.widgets.contact.js
1010 ms
navigation.js
1010 ms
jquery.easing.js
920 ms
jquery.fittext.js
1005 ms
jquery.localscroll.js
1006 ms
jquery.scrollto.js
1008 ms
jquery.appear.js
1008 ms
jquery.waitforimages.js
869 ms
jquery.bxslider.js
924 ms
jquery.fitvids.js
1001 ms
shortcodes.js
1002 ms
main.js
1004 ms
custom.js
868 ms
pixelentity.controller.js
868 ms
init.js
925 ms
jquery.form.min.js
1007 ms
scripts.js
1010 ms
wp-embed.min.js
933 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
4 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
6 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
11 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
12 ms
entypo-icon-font.woff
1154 ms
logo.png
1007 ms
Fotolia_82279160_M2.jpg
1665 ms
logo31.jpg
1001 ms
rotator3.jpg
1105 ms
loading.gif
864 ms
project-next.png
1003 ms
project-prev.png
1004 ms
close.png
1007 ms
006_Page_01-545x344.png
1667 ms
7273image_large-545x344.jpg
1150 ms
7279image_large-545x344.jpg
1145 ms
7277image_large-545x344.jpg
1143 ms
7275image_large-545x344.jpg
1144 ms
7281image_large-545x344.jpg
1237 ms
7276image_large-545x344.jpg
1287 ms
7278image_large-545x344.jpg
1285 ms
7297image_large-545x344.jpg
1283 ms
7298image_large-545x344.jpg
1279 ms
7299image_large-545x344.jpg
1378 ms
7762image_large-545x344.jpg
1375 ms
bcg-footer.png
1293 ms
sherlockholmes.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
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
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.
sherlockholmes.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
Issues were logged in the Issues panel in Chrome Devtools
sherlockholmes.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sherlockholmes.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 Sherlockholmes.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.
sherlockholmes.com
Open Graph description is not detected on the main page of Sherlock Holmes. 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: