27.3 sec in total
1.5 sec
25 sec
699 ms
Visit greenwave.fm now to see the best up-to-date Greenwave content for Thailand and also check out these interesting facts you probably never knew about greenwave.fm
เพลงดีดี กับความรู้สึกดีดี
Visit greenwave.fmWe analyzed Greenwave.fm page load time and found that the first response time was 1.5 sec and then it took 25.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
greenwave.fm performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value19.2 s
0/100
25%
Value22.3 s
0/100
10%
Value2,410 ms
5/100
30%
Value0.688
7/100
15%
Value30.7 s
0/100
10%
1547 ms
1516 ms
1049 ms
1070 ms
1072 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 50% of them (54 requests) were addressed to the original Greenwave.fm, 24% (26 requests) were made to Embed.atimemedia.com and 12% (13 requests) were made to Ads.atimeonline.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Greenwave.fm.
Page size can be reduced by 1.1 MB (48%)
2.2 MB
1.1 MB
In fact, the total size of Greenwave.fm 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 45.0 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 45.0 kB or 80% of the original size.
Potential reduce by 365.3 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, Greenwave needs image optimization as it can save up to 365.3 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 405.1 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 405.1 kB or 72% of the original size.
Potential reduce by 242.6 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. Greenwave.fm needs all CSS files to be minified and compressed as it can save up to 242.6 kB or 82% of the original size.
Number of requests can be reduced by 40 (41%)
97
57
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenwave. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
greenwave.fm
1547 ms
uikit.almost-flat.min.css
1516 ms
sticky.almost-flat.min.css
1049 ms
uikit.menu.primary.css
1070 ms
SukhumvitSet-All.css
1072 ms
button.min.css
1083 ms
comment.min.css
1090 ms
divider.min.css
1481 ms
form.min.css
1519 ms
header.min.css
1523 ms
icon.min.css
1539 ms
label.min.css
1542 ms
jquery.fancybox.css
610 ms
slick.css
1881 ms
home.css
629 ms
jquery-1.12.2.min.js
3125 ms
jquery-migrate-1.3.0.min.js
1936 ms
uikit.min.js
2876 ms
sticky.min.js
1993 ms
flowplayer-3.2.11.js
2468 ms
slick.min.js
3087 ms
jquery.fancybox.js
1540 ms
jquery.mousewheel-3.0.6.pack.js
664 ms
moment-with-locales.min.js
2907 ms
jquery.parallax.js
1432 ms
jquery.atimeAuth.beta.js
1613 ms
main.js
1425 ms
asyncjs.php
1220 ms
Highlight.jpg
20450 ms
official_fanpage1.png
742 ms
gw_fanpage.png
747 ms
link_cfd.jpg
1293 ms
link_cnp.jpg
1897 ms
link_gfc.jpg
1227 ms
link_mst.jpg
1917 ms
link_gch.jpg
3536 ms
link_gt.jpg
3979 ms
btn_tel.png
2392 ms
btn_ar_l.png
2493 ms
btn_ar_r.png
3083 ms
btn_gallery.png
3480 ms
btn_register.png
3555 ms
btn_shiftdj.png
3862 ms
atime_footer.png
4017 ms
greenwave_footer.png
4408 ms
HIGHTLIGHT-GT.jpg
20445 ms
CVNP---MARCH-final.jpg
19416 ms
hilight_gm.jpg
14178 ms
FIET-2.jpg
11195 ms
FIET-1.jpg
13985 ms
DEW-%E0%B8%AD%E0%B8%A3%E0%B8%B8%E0%B8%93.jpg
16622 ms
BAM-%E0%B8%AD%E0%B9%80%E0%B8%A1%E0%B8%A3%E0%B8%B4%E0%B8%81%E0%B8%B2.jpg
20445 ms
GW-logo.png
271 ms
sdk.js
276 ms
afr.php
163 ms
bg.jpg
7711 ms
glass1.png
11334 ms
glass2.png
11993 ms
glass3.png
13659 ms
bg_level3.png
6545 ms
play-green.png
267 ms
afr.php
877 ms
bg_clubfriday.png
5505 ms
cfd_logo.png
7081 ms
dot_v.png
7618 ms
btn_send_story_left.png
8192 ms
btn_send_story_right.png
8728 ms
bg_fanpage.png
8762 ms
bg_goodmusic.png
9243 ms
head_goodmusic.png
9782 ms
bg_more.png
9787 ms
bg_act_link.png
10308 ms
bg_tel.png
10817 ms
icon_msg.png
10820 ms
SukhumvitSet-Medium.woff
1417 ms
SukhumvitSet-Text.woff
844 ms
SukhumvitSet-Thin.woff
2018 ms
green_arrow.png
11378 ms
border_footer.png
11806 ms
SukhumvitSet-Bold.woff
1476 ms
fontawesome-webfont.woff
3637 ms
analytics.js
123 ms
get
1458 ms
nowplaying
2495 ms
user_login.png
11718 ms
afr.php
2 ms
afr.php
982 ms
asyncspc.php
973 ms
collect
3 ms
collect
81 ms
90 ms
xd_arbiter.php
218 ms
xd_arbiter.php
433 ms
get
2506 ms
arrow_left.png
11589 ms
arrow_right.png
13147 ms
get
2508 ms
2e428c93de05c4f7ad0f07664704ab46.jpg
8403 ms
lg.php
813 ms
a2307e4dd9613572050811c2efd6d025.jpg
2599 ms
lg.php
895 ms
df82d1182e9dddb5cf4487c87465764d.jpg
2100 ms
lg.php
1176 ms
lg.php
1176 ms
btn_connect_fb.png
1097 ms
avatar_medium.jpg
1370 ms
avatar_medium.jpg
574 ms
nowplaying
1006 ms
greenwave.fm 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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
greenwave.fm 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
greenwave.fm SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenwave.fm 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 Greenwave.fm 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.
greenwave.fm
Open Graph data is detected on the main page of Greenwave. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: