9.9 sec in total
3.3 sec
6.4 sec
242 ms
Welcome to prism.co.jp homepage info - get ready to check Prism best content for Japan right away, or after learning these important things about prism.co.jp
製造業専門の総合検索サイト「プリズム(prism.co.jp)」。お探しの製品・会社がきっと見つかる!
Visit prism.co.jpWe analyzed Prism.co.jp page load time and found that the first response time was 3.3 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
prism.co.jp performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value16.4 s
0/100
25%
Value18.3 s
0/100
10%
Value180 ms
92/100
30%
Value0.475
18/100
15%
Value16.2 s
5/100
10%
3298 ms
375 ms
383 ms
557 ms
392 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 91% of them (83 requests) were addressed to the original Prism.co.jp, 3% (3 requests) were made to Google.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Prism.co.jp.
Page size can be reduced by 1.2 MB (73%)
1.7 MB
451.1 kB
In fact, the total size of Prism.co.jp main page is 1.7 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 165.5 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. This page needs HTML code to be minified as it can gain 55.6 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 165.5 kB or 88% of the original size.
Potential reduce by 9.1 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. Prism images are well optimized though.
Potential reduce by 983.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 983.8 kB or 76% of the original size.
Potential reduce by 91.5 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. Prism.co.jp needs all CSS files to be minified and compressed as it can save up to 91.5 kB or 81% of the original size.
Number of requests can be reduced by 55 (61%)
90
35
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prism. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
prism.co.jp
3298 ms
PanelBar.Sunset.css
375 ms
Grid.Prism.css
383 ms
Grid.Default.css
557 ms
TabStrip.Default.css
392 ms
ComboBox.Default.css
602 ms
PanelBar.Default.css
551 ms
swfobject.js
563 ms
fancy.css
585 ms
jquery-1.2.3.pack.js
1071 ms
jquery.metadata.js
762 ms
jquery.pngFix.pack.js
761 ms
jquery.fancybox-1.0.0.js
960 ms
jsapi
17 ms
translation.js
796 ms
jquery.toggleval.js
942 ms
StyleSheet.css
963 ms
WebResource.axd
1004 ms
WebResource.axd
1088 ms
WebResource.axd
1119 ms
WebResource.axd
1147 ms
WebResource.axd
1143 ms
WebResource.axd
1204 ms
WebResource.axd
1246 ms
WebResource.axd
1259 ms
WebResource.axd
1507 ms
ScriptResource.axd
1496 ms
Telerik.Web.UI.WebResource.axd
2437 ms
wz_tooltip.js
859 ms
12 ms
default+en.I.js
3 ms
Login.gif
266 ms
logo.gif
245 ms
DefaultTabStripSelectedItem.gif
421 ms
DefaultTabStripManager.gif
424 ms
DefaultTabStripJob.gif
427 ms
DefaultTabStripBoard.gif
451 ms
DefaultTabStripEvent.gif
654 ms
About.gif
651 ms
Help.gif
653 ms
SearchButton.gif
692 ms
BlackHint.gif
678 ms
BlueArrowRight.gif
829 ms
InsertItem.gif
837 ms
HeaderFoot.gif
835 ms
Reset.gif
879 ms
Plus.gif
870 ms
22499_.jpg
1035 ms
29314_.jpg
1050 ms
29189_.jpg
1076 ms
29187_.jpg
1079 ms
32037_.jpg
1096 ms
28201_.jpg
1250 ms
27981_.jpg
1291 ms
24942_.jpg
1292 ms
24327_.jpg
1293 ms
24341_.jpg
1355 ms
LoadItem3.gif
1356 ms
toku_indus_side.gif
1777 ms
27378.gif
1636 ms
27130.jpg
1820 ms
Inquiry.gif
1523 ms
HeaderHead.gif
245 ms
HeaderBody.gif
262 ms
SearchPanel.gif
360 ms
CategoryHead.gif
443 ms
CategoryBody.gif
445 ms
MainCategorypassive.gif
535 ms
CategoryFoot.gif
537 ms
SpecialHead.gif
641 ms
SpecialBody.gif
632 ms
ItemHead.gif
671 ms
ItemBody.gif
713 ms
WebResource.axd
715 ms
ItemFoot.gif
717 ms
sprite.gif
832 ms
SpecialFoot.gif
839 ms
BannerHead2.gif
848 ms
BannerBody.gif
889 ms
BannerFoot.gif
890 ms
FilterHead.gif
896 ms
FilterBody.gif
1019 ms
FilterFoot.gif
1036 ms
BannerHead.gif
1022 ms
FooterHead.gif
1066 ms
FooterBody.gif
1065 ms
ga.js
9 ms
tag.js
118 ms
__utm.gif
23 ms
tag
12 ms
ya.js
307 ms
prism.co.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
Image elements do not have [alt] attributes
Links do not have a discernible name
prism.co.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prism.co.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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prism.co.jp 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 Prism.co.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.
prism.co.jp
Open Graph description is not detected on the main page of Prism. 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: