6.4 sec in total
1.1 sec
5 sec
300 ms
Welcome to protec.ne.jp homepage info - get ready to check Protec best content right away, or after learning these important things about protec.ne.jp
株式会社日本プロテックは、建築パース、CGパース、3DCGアニメーション、VR(360度映像)CG各種コンテンツ制作をしている制作会社です。CGパース、VR、コンテンツ制作は全国対応可能です。
Visit protec.ne.jpWe analyzed Protec.ne.jp page load time and found that the first response time was 1.1 sec and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
protec.ne.jp performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value19.2 s
0/100
25%
Value12.0 s
4/100
10%
Value1,670 ms
11/100
30%
Value0.348
32/100
15%
Value16.7 s
5/100
10%
1088 ms
344 ms
1209 ms
354 ms
545 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original Protec.ne.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Protec.ne.jp.
Page size can be reduced by 134.8 kB (37%)
364.4 kB
229.5 kB
In fact, the total size of Protec.ne.jp main page is 364.4 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. 20% of websites need less resources to load. Javascripts take 164.0 kB which makes up the majority of the site volume.
Potential reduce by 17.9 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 17.9 kB or 74% of the original size.
Potential reduce by 4.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. Protec images are well optimized though.
Potential reduce by 97.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 97.8 kB or 60% of the original size.
Potential reduce by 15.0 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. Protec.ne.jp needs all CSS files to be minified and compressed as it can save up to 15.0 kB or 75% of the original size.
Number of requests can be reduced by 33 (52%)
63
30
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Protec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.protec.ne.jp
1088 ms
ccm.base.css
344 ms
jquery.js
1209 ms
ccm.base.js
354 ms
fancyzoom.min.js
545 ms
ccm.tnspacer.css
374 ms
view.css
514 ms
jquery.fancybox-1.3.1.css
525 ms
jquery.fancybox-1.3.1.pack.js
881 ms
view.css
560 ms
main.css
799 ms
mjl.js
1230 ms
run.js
726 ms
lightbox.css
862 ms
set.css
363 ms
font.css
322 ms
base.css
455 ms
style.css
387 ms
header_bg.gif
178 ms
header_r_bg.gif
189 ms
logo.gif
184 ms
list01.gif
174 ms
gnavi01.gif
178 ms
gnavi02.gif
172 ms
gnavi03.gif
343 ms
gnavi04.gif
347 ms
gnavi05.gif
352 ms
tt01.gif
353 ms
cg_bg.jpg
363 ms
cg_img_off.jpg
558 ms
web_bg.jpg
512 ms
pv_img_off.jpg
690 ms
contents_bg.jpg
527 ms
contents_img.jpg
884 ms
fe22d1db289f6d1fb0bf70339652cff1.jpg
724 ms
b0cce427f4e798d53843e11aadd967a0.jpg
851 ms
0e04d73271a607b1bd0e6fcc0f2ca280.jpg
877 ms
20f867f520a9b61348249fe29349582a.jpg
743 ms
96dddc00abbb6fb59e4fc55c53f6bea8.jpg
1033 ms
ee51ef9245d96a3aa648ed84b11280ce.jpg
1086 ms
d63b1ce966cc77c8d8e43d4d4227834e.jpg
930 ms
74438f839e4b42545339c8f1688774fe.jpg
1191 ms
btn_sample.gif
1053 ms
bn_3dar.jpg
1232 ms
bn_tachpanel.jpg
1489 ms
btn_pagetop.gif
1204 ms
side_contact.gif
1404 ms
menu01.jpg
1448 ms
menu02.jpg
1529 ms
bn_order.jpg
1376 ms
menuttl_cg.gif
1408 ms
menuttl_pv.gif
1549 ms
menuttl_contents.gif
1580 ms
news_01.gif
1541 ms
ga.js
17 ms
__utm.gif
14 ms
bg_menu.jpg
1467 ms
footer_bg.gif
1511 ms
closebox.png
1534 ms
gnavi01_o.gif
179 ms
gnavi02_o.gif
189 ms
gnavi03_o.gif
184 ms
gnavi04_o.gif
174 ms
gnavi05_o.gif
179 ms
protec.ne.jp 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
protec.ne.jp 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
Page has valid source maps
protec.ne.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Protec.ne.jp 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 Protec.ne.jp 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.
protec.ne.jp
Open Graph description is not detected on the main page of Protec. 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: