4.5 sec in total
1.1 sec
3.2 sec
165 ms
Click here to check amazing WOX content for Japan. Otherwise, check out these important facts you probably never knew about wox.cc
Website, blogs, message boards are all freely available web service. Expertise is not needed at all! It is safe even for beginners.
Visit wox.ccWe analyzed Wox.cc page load time and found that the first response time was 1.1 sec and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wox.cc performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.4 s
21/100
25%
Value7.0 s
32/100
10%
Value140 ms
96/100
30%
Value0.029
100/100
15%
Value5.2 s
75/100
10%
1118 ms
183 ms
362 ms
366 ms
366 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 47% of them (28 requests) were addressed to the original Wox.cc, 12% (7 requests) were made to Apis.google.com and 5% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Wox.cc.
Page size can be reduced by 80.0 kB (31%)
259.1 kB
179.1 kB
In fact, the total size of Wox.cc main page is 259.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 140.6 kB which makes up the majority of the site volume.
Potential reduce by 19.3 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 19.3 kB or 78% of the original size.
Potential reduce by 2.2 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. WOX images are well optimized though.
Potential reduce by 30.8 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 30.8 kB or 52% of the original size.
Potential reduce by 27.8 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. Wox.cc needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 82% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WOX. 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 5 to 1 for CSS and as a result speed up the page load time.
wox.cc
1118 ms
default.css
183 ms
site.css
362 ms
top.css
366 ms
followme.js
366 ms
wox.analyzer.wox.cc
1091 ms
bookmark_button.js
336 ms
plusone.js
85 ms
share.js
297 ms
ga.js
28 ms
button-only.gif
167 ms
site_top_bg.gif
183 ms
wox_top.png
182 ms
web.png
183 ms
blog.png
194 ms
bbs.png
350 ms
review.png
540 ms
novel.png
363 ms
gallery.png
542 ms
profile.png
370 ms
bookmark.png
385 ms
form.png
524 ms
pages.png
543 ms
counter.png
556 ms
analyzer.png
575 ms
head_L.gif
698 ms
head_R.gif
722 ms
body_R.gif
727 ms
prof_ss_none.gif
731 ms
foot_R.gif
760 ms
foot_L.gif
779 ms
www.png
886 ms
__utm.gif
22 ms
analyze
963 ms
widgets.js
11 ms
cb=gapi.loaded_0
22 ms
233 ms
share_button.html
299 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
54 ms
cb=gapi.loaded_1
32 ms
fastbutton
131 ms
twitter_logo.gif
741 ms
facebook_logo.gif
768 ms
postmessageRelay
48 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
12 ms
like.php
175 ms
api.js
49 ms
core:rpc:shindig.random:shindig.sha1.js
79 ms
2536007149-postmessagerelay.js
67 ms
cb=gapi.loaded_0
27 ms
cb=gapi.loaded_1
27 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
91 ms
jot
113 ms
reset.css
189 ms
entry-button.css
190 ms
vpc6VNjRPXV.js
154 ms
LVx-xkvaJ0b.png
171 ms
bt_check_2.png
32 ms
button-counter.gif
5 ms
wox.cc 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
wox.cc 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
wox.cc 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wox.cc can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Wox.cc 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.
wox.cc
Open Graph description is not detected on the main page of WOX. 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: