14 sec in total
3.8 sec
9.9 sec
306 ms
Click here to check amazing Weareharper content. Otherwise, check out these important facts you probably never knew about weareharper.com
Visit weareharper.comWe analyzed Weareharper.com page load time and found that the first response time was 3.8 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
weareharper.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value5.8 s
15/100
25%
Value4.0 s
81/100
10%
Value540 ms
54/100
30%
Value0.093
91/100
15%
Value6.5 s
58/100
10%
3777 ms
46 ms
283 ms
63 ms
490 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 60% of them (57 requests) were addressed to the original Weareharper.com, 19% (18 requests) were made to Scontent.cdninstagram.com and 11% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Weareharper.com.
Page size can be reduced by 1.7 MB (29%)
5.9 MB
4.2 MB
In fact, the total size of Weareharper.com main page is 5.9 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. 65% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 37.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 37.6 kB or 80% of the original size.
Potential reduce by 119.0 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. Weareharper images are well optimized though.
Potential reduce by 915.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 915.9 kB or 72% of the original size.
Potential reduce by 617.5 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. Weareharper.com needs all CSS files to be minified and compressed as it can save up to 617.5 kB or 86% of the original size.
Number of requests can be reduced by 45 (55%)
82
37
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weareharper. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
weareharper.com
3777 ms
css
46 ms
layerslider.css
283 ms
css
63 ms
styles.css
490 ms
instalink-1.5.0.min.css
562 ms
style.css
561 ms
font-awesome.min.css
674 ms
style.min.css
720 ms
stylesheet.min.css
1323 ms
woocommerce.min.css
728 ms
woocommerce_responsive.min.css
875 ms
style_dynamic.php
2464 ms
responsive.min.css
1140 ms
style_dynamic_responsive.php
2587 ms
js_composer.css
1029 ms
custom_css.php
2595 ms
greensock.js
1619 ms
jquery.js
1729 ms
jquery-migrate.min.js
1546 ms
layerslider.kreaturamedia.jquery.js
1792 ms
layerslider.transitions.js
1853 ms
instalink-1.5.0.min.js
1982 ms
jquery.form.min.js
2036 ms
scripts.js
2081 ms
jquery.blockUI.min.js
2246 ms
woocommerce.min.js
2272 ms
jquery.cookie.min.js
2312 ms
cart-fragments.min.js
2483 ms
qode-like.min.js
2508 ms
plugins.js
3449 ms
jquery.carouFredSel-6.2.1.min.js
2934 ms
lemmon-slider.min.js
2717 ms
jquery.fullPage.min.js
2748 ms
jquery.mousewheel.min.js
2818 ms
jquery.touchSwipe.min.js
2836 ms
isotope.pkgd.min.js
2971 ms
js
93 ms
default_dynamic.php
3831 ms
default.min.js
3287 ms
custom_js.php
3574 ms
comment-reply.min.js
2629 ms
ajax.min.js
2644 ms
js_composer_front.js
2759 ms
woocommerce.js
2725 ms
select2.min.js
3171 ms
wp-emoji-release.min.js
2827 ms
HARPER_BRAND_IdentityMASTER03.png
1051 ms
Xtra-Sml-Heart.jpg
1176 ms
WAH_CurlCurl_Photos_Summer_2016-13.jpg
2458 ms
WAH_CurlCurl_Photos_Summer_2016-15.jpg
1860 ms
WAH_CurlCurl_Photos_Summer_2016-34.jpg
2605 ms
WAH_CurlCurl_Photos_Summer_2016-37.jpg
3361 ms
WAH_CurlCurl_Photos_Summer_2016-7.jpg
2871 ms
Super-Soft.png
3483 ms
Super-Soft-1.png
2350 ms
Super-Soft-2.png
2856 ms
FutureUnity_V4-e1427361745297-300x83.png
2703 ms
ga.js
21 ms
do7-0avPC2vxor6SN2THGA.ttf
39 ms
Li18TEFObx_yGdzKDoI_ci3USBnSvpkopQaUR-2r7iU.ttf
39 ms
ZKwULyCG95tk6mOqHQfRBC3USBnSvpkopQaUR-2r7iU.ttf
39 ms
cbAbzEjxTdN5KKmS-gA0tS3USBnSvpkopQaUR-2r7iU.ttf
39 ms
rr0ijB5_2nAJsAoZ6vECXaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
STBOO2waD2LpX45SXYjQBS3USBnSvpkopQaUR-2r7iU.ttf
41 ms
WmVKXVcOuffP_qmCpFuyzS3USBnSvpkopQaUR-2r7iU.ttf
40 ms
QoPu455RxV2raYSIFXAMBS3USBnSvpkopQaUR-2r7iU.ttf
40 ms
Ji5epXNcpHu3r63lhS0cTi3USBnSvpkopQaUR-2r7iU.ttf
39 ms
fontawesome-webfont.woff
2855 ms
__utm.gif
16 ms
collect
55 ms
search
139 ms
instagram.GIF
1447 ms
1444195703
50 ms
recent
206 ms
10474976_579614538860644_196280033_n.jpg
288 ms
254 ms
916405_172405786478603_407765140_n.jpg
349 ms
10549909_1686800384935231_25043967_n.jpg
479 ms
923670_1685299451726426_953990738_n.jpg
509 ms
12530859_1692076867734730_1111649747_n.jpg
568 ms
10729255_1578571089131408_472766591_n.jpg
587 ms
11821803_865961883529556_107891944_n.jpg
587 ms
10012427_1748186755417015_406829746_n.jpg
487 ms
1169848_1052091341495634_1030166785_n.jpg
587 ms
12530856_204935586530215_2121526411_n.jpg
598 ms
12826259_520357748147565_1481543869_n.jpg
585 ms
12798183_537721289722759_1332518759_n.jpg
659 ms
12826204_587392518094185_590646596_n.jpg
662 ms
12751541_561571500665672_926090201_n.jpg
677 ms
12822416_848210838642003_1778249248_n.jpg
736 ms
12816795_234066093605034_615383207_n.jpg
689 ms
12798009_202373563457663_76672522_n.jpg
720 ms
10724031_504905003045582_1222428712_n.jpg
797 ms
eNfH7kLpF1PZWpsetF-hawhNokzbzq3DXZOMIjhroK4.ttf
5 ms
weareharper.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
weareharper.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
weareharper.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 Weareharper.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 Weareharper.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.
weareharper.com
Open Graph description is not detected on the main page of Weareharper. 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: