4.4 sec in total
351 ms
3.8 sec
240 ms
Visit wewereevergreen.com now to see the best up-to-date Wewereevergreen content and also check out these interesting facts you probably never knew about wewereevergreen.com
We Were Evergreen, the official website, music, gigs, events
Visit wewereevergreen.comWe analyzed Wewereevergreen.com page load time and found that the first response time was 351 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wewereevergreen.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value4.6 s
35/100
25%
Value5.9 s
47/100
10%
Value180 ms
92/100
30%
Value0.171
70/100
15%
Value4.1 s
87/100
10%
351 ms
1100 ms
29 ms
45 ms
55 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wewereevergreen.com, 43% (31 requests) were made to Musicwwe.com and 7% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Musicwwe.com.
Page size can be reduced by 1.2 MB (49%)
2.5 MB
1.3 MB
In fact, the total size of Wewereevergreen.com main page is 2.5 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.2 MB which makes up the majority of the site volume.
Potential reduce by 407 B
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 407 B or 48% of the original size.
Potential reduce by 244.6 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. Obviously, Wewereevergreen needs image optimization as it can save up to 244.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 659.0 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 659.0 kB or 71% of the original size.
Potential reduce by 320.2 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. Wewereevergreen.com needs all CSS files to be minified and compressed as it can save up to 320.2 kB or 83% of the original size.
Number of requests can be reduced by 49 (75%)
65
16
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wewereevergreen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
wewereevergreen.com
351 ms
www.musicwwe.com
1100 ms
css
29 ms
css
45 ms
css
55 ms
css
53 ms
css
54 ms
style.css
242 ms
settings.css
167 ms
comment-reply.js
177 ms
sb-instagram.css
165 ms
font-awesome.min.css
12 ms
mb.YTPlayer.css
289 ms
jquery.js
476 ms
effects.js
648 ms
easing.js
290 ms
hoverIntent.js
291 ms
flexslider-min.js
324 ms
superfish.js
331 ms
quicksand.js
338 ms
tipTip.js
357 ms
form_validation.js
418 ms
mobilemenu.js
438 ms
backstretch.js
437 ms
custom.js
440 ms
bit_widget.js
9 ms
fsml-base.css
517 ms
buttons.js
11 ms
sb-instagram.js
517 ms
jquery.mb.YTPlayer.min.js
607 ms
wp-embed.min.js
553 ms
fsml-hideshow.js
563 ms
bit_widget.js
28 ms
wp-emoji-release.min.js
424 ms
analytics.js
8 ms
Hollow-Man.png
1730 ms
ajax-loader.gif
222 ms
up.png
222 ms
tumblr.png
220 ms
facebook.png
221 ms
Twitter.png
220 ms
youtube.png
278 ms
iframe_api
180 ms
getAllAppDefault.esi
124 ms
collect
22 ms
oPxV1dkj-zBXVn8gGPEP7w.ttf
15 ms
www-widgetapi.js
29 ms
getSegment.php
22 ms
checkOAuth.esi
15 ms
t.dhj
8 ms
t.dhj
19 ms
chCoUv-MdGI
50 ms
cm
30 ms
x35248
219 ms
s-3271.xgi
7 ms
hbpix
30 ms
13 ms
www-embed-player-vflfNyN_r.css
15 ms
www-embed-player.js
29 ms
base.js
51 ms
xrefid.xgi
12 ms
35 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
39 ms
ad_status.js
38 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
37 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
pixel
15 ms
pixel
14 ms
2981
27 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
9 ms
buttons.ab966a004186897711de4a5ed256c924.css
11 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
8 ms
wewereevergreen.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.
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
wewereevergreen.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
wewereevergreen.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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wewereevergreen.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Wewereevergreen.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.
wewereevergreen.com
Open Graph description is not detected on the main page of Wewereevergreen. 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: