4.4 sec in total
873 ms
3.2 sec
300 ms
Visit webcg.net now to see the best up-to-date WebCG content for Japan and also check out these interesting facts you probably never knew about webcg.net
1962年創刊の自動車専門誌『CAR GRAPHIC』のインターネットサイトとして、1998年6月にオープンした『webCG』。新車情報はもちろん、プロフェッショナルによる試乗記やクルマにまつわる読み物など、クルマ好きに向けて日々情報を発信中です。
Visit webcg.netWe analyzed Webcg.net page load time and found that the first response time was 873 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
webcg.net performance score
name
value
score
weighting
Value5.0 s
9/100
10%
Value13.3 s
0/100
25%
Value23.8 s
0/100
10%
Value35,190 ms
0/100
30%
Value0.267
46/100
15%
Value50.7 s
0/100
10%
873 ms
632 ms
40 ms
5 ms
32 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original Webcg.net, 49% (38 requests) were made to Webcg.ismcdn.jp and 8% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (917 ms) relates to the external source Harpoon3.userdive.com.
Page size can be reduced by 576.7 kB (31%)
1.9 MB
1.3 MB
In fact, the total size of Webcg.net main page is 1.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 939.6 kB which makes up the majority of the site volume.
Potential reduce by 126.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 126.0 kB or 73% of the original size.
Potential reduce by 10.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. WebCG images are well optimized though.
Potential reduce by 422.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 422.9 kB or 59% of the original size.
Potential reduce by 17.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. Webcg.net needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 51% of the original size.
Number of requests can be reduced by 25 (32%)
77
52
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WebCG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.webcg.net
873 ms
base.css
632 ms
satelliteLib-6f6d3340fdf1e13d57f2665365a80244ef669f69.js
40 ms
adsbygoogle.js
5 ms
jquery.min.js
32 ms
jquery-ui.min.js
52 ms
lazysizes.min.js
412 ms
tools-gallery.js
412 ms
l.js
171 ms
gpt.js
56 ms
hqdefault.jpg
90 ms
img_f6609ef5f26030fff481ed4d2ef94e1812299.gif
547 ms
img_027a7e476b841f7d2ae5d0a7eaa5026510094.png
546 ms
img_b976f2f78b56088b66e574bbba3195149742.png
546 ms
img_ff80b84804471e211c350527325f6b186389.png
594 ms
logo.png
284 ms
img_2df776b64120d4215df954812d945b5a104525.jpg
421 ms
img_3b82e073cc1273618977daddff20282a110617.jpg
426 ms
img_cb3f2546db4d751ddd1e4d55a0b1ecd2110579.jpg
602 ms
img_1eb60ae0cf448d76bc59151d594ce492101478.jpg
594 ms
img_5780a225fce191d9eea67a90bbad6851237494.jpg
806 ms
lazyload.gif
428 ms
pubads_impl_81.js
38 ms
feed-icon-28x28.png
558 ms
icon_category_v2.png
564 ms
ads
321 ms
container.html
51 ms
ca-pub-6387115476692568.js
166 ms
zrt_lookup.html
158 ms
show_ads_impl.js
51 ms
ga.js
116 ms
5000037778-img-fe
607 ms
satellite-56a0c4db64746d31fc000ff8.js
62 ms
s-code-contents-a626fd076248e1b786c5d68ba8b45def7cc71992.js
146 ms
m.gif
411 ms
ads
250 ms
osd.js
54 ms
UDTracker.js
917 ms
top_feature_hot.png
333 ms
__utm.gif
18 ms
__utm.gif
16 ms
ad58821.jpg
858 ms
expansion_embed.js
12 ms
10457902206211133981
28 ms
abg.js
29 ms
m_js_controller.js
48 ms
googlelogo_color_112x36dp.png
21 ms
googlelogo_color_112x36dp.png
64 ms
14706322608479754516
62 ms
s
28 ms
x_button_blue2.png
28 ms
s41606675018556
9 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
3 ms
img_6f9c7f0f293003fe94adb890657bbaf262269.jpg
364 ms
img_69e9f6f78c01a14617371521ed2936df52200.jpg
180 ms
img_a3133e73972b65d28d099a04ca41249f110659.jpg
193 ms
img_7ca79ee9d38fa43ea06f4c55009f3edd268607.jpg
204 ms
img_5780a225fce191d9eea67a90bbad6851237494.jpg
205 ms
img_01c105277165f84934a374f70abbeea3333875.jpg
358 ms
img_f87af50da4272e4796d10c9e8d0d65e1369184.jpg
563 ms
img_7ea5431860495d1777e742e27af1665f67792.jpg
389 ms
img_99dc2d91cf373af851880685b929f99c55204.jpg
387 ms
img_17df5a1d1d77dda15e46ece4ed98527c111582.jpg
397 ms
img_7915ccd28071cc1fab5319bdd1717d9c120688.jpg
535 ms
img_ded547739b94d949866dcff0398252c7113445.jpg
545 ms
img_6e895e7a9b1f79b07b1bbee22f9dfaf2107725.jpg
573 ms
img_d7dc9df4f2adb24442bc438dfaf9c3c5104932.jpg
575 ms
img_5780a225fce191d9eea67a90bbad6851237494.jpg
585 ms
img_3b82e073cc1273618977daddff20282a110617.jpg
716 ms
img_2df776b64120d4215df954812d945b5a104525.jpg
190 ms
img_3b82e073cc1273618977daddff20282a110617.jpg
188 ms
img_cb3f2546db4d751ddd1e4d55a0b1ecd2110579.jpg
191 ms
img_1eb60ae0cf448d76bc59151d594ce492101478.jpg
185 ms
img_1eb60ae0cf448d76bc59151d594ce492101478.jpg
192 ms
img_dbfbbae1a4e2b79117462a04e581a0b483111.jpg
291 ms
img_cb3f2546db4d751ddd1e4d55a0b1ecd2110579.jpg
366 ms
img_01c105277165f84934a374f70abbeea3333875.jpg
370 ms
img_e56b66fd575320e4abd1dbf86eaa9d2e227745.jpg
371 ms
webcg.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
webcg.net 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
webcg.net 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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webcg.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Webcg.net 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.
webcg.net
Open Graph data is detected on the main page of WebCG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: