5.8 sec in total
762 ms
4.8 sec
151 ms
Visit god-tongue.com now to see the best up-to-date God Tongue content for Japan and also check out these interesting facts you probably never knew about god-tongue.com
Visit god-tongue.comWe analyzed God-tongue.com page load time and found that the first response time was 762 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
god-tongue.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.1 s
1/100
25%
Value8.5 s
18/100
10%
Value60 ms
100/100
30%
Value0.406
24/100
15%
Value6.1 s
63/100
10%
762 ms
334 ms
511 ms
511 ms
539 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 45% of them (34 requests) were addressed to the original God-tongue.com, 12% (9 requests) were made to Plugins.mixi.jp and 11% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain God-tongue.com.
Page size can be reduced by 493.6 kB (32%)
1.6 MB
1.1 MB
In fact, the total size of God-tongue.com main page is 1.6 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. 60% of websites need less resources to load. Images take 874.4 kB which makes up the majority of the site volume.
Potential reduce by 18.7 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 18.7 kB or 71% of the original size.
Potential reduce by 28.7 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. God Tongue images are well optimized though.
Potential reduce by 408.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 408.5 kB or 66% of the original size.
Potential reduce by 37.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. God-tongue.com needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 83% of the original size.
Number of requests can be reduced by 33 (45%)
73
40
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of God Tongue. 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 5 to 1 for CSS and as a result speed up the page load time.
god-tongue.com
762 ms
style_2014_kiss_top_body.css
334 ms
style_2014_kiss_top.css
511 ms
colorbox.css
511 ms
zoombox.css
539 ms
jquery.min.js
26 ms
jquery.easing.1.3.js
556 ms
jquery.colorbox-min.js
555 ms
jquery.12loader.js
497 ms
jquery.12rolloverMenuFade.js
662 ms
jquery.12rolloverImageFade.js
679 ms
2014_kiss_top.js
680 ms
sns_fb.gif
235 ms
sns_tw.gif
236 ms
sns_tw2.gif
185 ms
2014_kiss_top_logo.png
1268 ms
2014_kiss_top_koukai2.png
353 ms
2014_top_DVD.png
541 ms
2014_kiss_top_douga_off.png
1021 ms
2014_kiss_top_douga_on.png
1090 ms
2014_top_ftr.gif
765 ms
bnr_HMV.jpg
1031 ms
godtongue_kiss_236x58.jpg
1192 ms
bnr_kiss2013.jpg
948 ms
bnr_majiuta2014.jpg
1350 ms
bnr_tvtokyo.gif
1191 ms
sdk.js
278 ms
widgets.js
36 ms
plusone.js
141 ms
plugins.js
306 ms
share
340 ms
2014_kiss_top_pt.jpg
2344 ms
2014_kiss_top_menu_2_off.png
1404 ms
2014_kiss_top_menu_1_off.png
1313 ms
2014_kiss_top_menu_3_off.png
1307 ms
overlay.png
1399 ms
2014_kiss_top_menu_1_on.png
1704 ms
2014_kiss_top_menu_2_on.png
1637 ms
2014_kiss_top_menu_3_on.png
1482 ms
kiss_preloader.gif
2302 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
22 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
44 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
18 ms
fastbutton
69 ms
postmessageRelay
55 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
27 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
26 ms
3193398744-postmessagerelay.js
42 ms
rpc:shindig_random.js
40 ms
jot
97 ms
138 ms
cb=gapi.loaded_0
5 ms
xd_arbiter.php
212 ms
xd_arbiter.php
417 ms
jquery-1.7.2.min.js
8 ms
btn_iine_20.png
325 ms
favorite.pl
382 ms
like.php
96 ms
wy1X4hBW7e7.js
493 ms
LVx-xkvaJ0b.png
554 ms
mixi_check_entry.css
9 ms
errorreport.production.js
296 ms
json.js
296 ms
underscore-string-1.3.3-2.0.0-compress.js
298 ms
namespace-brook-compress.js
298 ms
prototype-effects-1.6.1-1.8.3-compress.js
446 ms
mixi.js
305 ms
favorite.production.js
588 ms
jquery-1.7.1.min-noconflict-compress.js
741 ms
analytics.js
15 ms
comment001.gif
10 ms
favorite_button004.png
17 ms
comment_content_top001.gif
12 ms
god-tongue.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
Image elements do not have [alt] attributes
Links do not have a discernible name
god-tongue.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
Page has valid source maps
god-tongue.com 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
JA
N/A
ISO-2022-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise God-tongue.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that God-tongue.com main page’s claimed encoding is iso-2022-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
god-tongue.com
Open Graph data is detected on the main page of God Tongue. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: