11.1 sec in total
2.4 sec
8.4 sec
343 ms
Click here to check amazing O S P content for India. Otherwise, check out these important facts you probably never knew about o-s-p.net
ルアーフィッシングメーカーO.S.P,Inc.の公式サイトです。
Visit o-s-p.netWe analyzed O-s-p.net page load time and found that the first response time was 2.4 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
o-s-p.net performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value18.2 s
0/100
25%
Value16.1 s
0/100
10%
Value770 ms
38/100
30%
Value0.685
7/100
15%
Value20.3 s
2/100
10%
2357 ms
337 ms
26 ms
679 ms
1048 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 88% of them (84 requests) were addressed to the original O-s-p.net, 3% (3 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain O-s-p.net.
Page size can be reduced by 418.6 kB (10%)
4.1 MB
3.6 MB
In fact, the total size of O-s-p.net main page is 4.1 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 3.6 MB which makes up the majority of the site volume.
Potential reduce by 64.6 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 64.6 kB or 81% of the original size.
Potential reduce by 87.0 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. O S P images are well optimized though.
Potential reduce by 153.4 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 153.4 kB or 67% of the original size.
Potential reduce by 113.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. O-s-p.net needs all CSS files to be minified and compressed as it can save up to 113.6 kB or 78% of the original size.
Number of requests can be reduced by 29 (31%)
94
65
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O S P. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.o-s-p.net
2357 ms
styles.css
337 ms
css
26 ms
genericons.css
679 ms
style.css
1048 ms
pagenavi-css.css
368 ms
jquery.js
1126 ms
jquery-migrate.min.js
662 ms
jquery.min.js
29 ms
scrollsmoothly.js
734 ms
slides.min.jquery.js
827 ms
lightbox_plus_min.js
677 ms
jquery.colorbox.js
727 ms
common.js
750 ms
swfobject.js
416 ms
pc-top.css
184 ms
pc-common.css
184 ms
analytics.js
30 ms
tit_logo.gif
196 ms
btn_english.gif
194 ms
img_top_varuna_spec2sf.jpg
875 ms
img_top_rudra130msf.jpg
1290 ms
img_top_main_highpitcher1oz.jpg
993 ms
eco_banner.jpg
768 ms
img_top_main151026override.jpg
849 ms
img_top_main151026highcut.jpg
727 ms
img_top_main150819.jpg
1092 ms
img_top_mainshadtail.jpg
1144 ms
img_top_main14093001.jpg
1357 ms
icon_newproduct.gif
1048 ms
icon_shipment.gif
1157 ms
icon_media.gif
1222 ms
icon_event.gif
1274 ms
icon_tournament.gif
1332 ms
icon_info.gif
1324 ms
img_kawamurakoutaro.jpg
1395 ms
img_odakeita.jpg
1454 ms
img_mimurakazuhiro.jpg
1469 ms
img_tomimuratakaaki.jpg
1488 ms
img_urakawamasanori.jpg
1516 ms
img_kitayaatoshimichi.jpg
1522 ms
img_yamazoedaisuke.jpg
1567 ms
img_miaketakahiro.jpg
1632 ms
img_tsujiinobuyuki.jpg
1653 ms
img_hayakawajunichi.jpg
1651 ms
img_uedaseikan.jpg
1702 ms
img_miyamotoyouhei.jpg
1691 ms
img_mikamishota.jpg
1741 ms
1021.jpg
1996 ms
0023.jpg
2145 ms
img_motegishogo.jpg
1835 ms
img_hayashikoudai.jpg
1861 ms
img_yamaokakazufumi.jpg
1890 ms
sdk.js
178 ms
img_moritatetsuhiro.jpg
1911 ms
widgets.js
7 ms
collect
17 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
37 ms
img_hashimototakuya.jpg
1838 ms
img_kusabukayukinori.jpg
1827 ms
135 ms
xd_arbiter.php
140 ms
xd_arbiter.php
263 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
13 ms
jot
97 ms
img_takeuchikazuhiro.jpg
1359 ms
icon_arrow03.gif
1333 ms
1602232109_s.jpg
1340 ms
btn_kids.jpg
1342 ms
bnr_price.gif
1221 ms
bnr_ospreyseye.jpg
1228 ms
bnr_namiki.jpg
1185 ms
bnr_journal.gif
1176 ms
bnr_twitter.gif
1209 ms
bg_menu.gif
1160 ms
top_tit_hottopics.gif
1123 ms
txt_more.gif
1176 ms
icon_arrow02.gif
1124 ms
top_tit_report.gif
1153 ms
icon_arrow05.gif
1195 ms
icon_arrow01.gif
1154 ms
btn_pagetop.gif
1125 ms
overlay.png
1153 ms
controls.png
1159 ms
border.png
1132 ms
loading_background.png
1205 ms
loading.gif
1150 ms
prev.png
1128 ms
next.png
1144 ms
prev.gif
1180 ms
next.gif
1120 ms
expand.gif
1184 ms
close.gif
1166 ms
zzoop.gif
1801 ms
sp-top.css
183 ms
sp-common.css
184 ms
o-s-p.net 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
o-s-p.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
Issues were logged in the Issues panel in Chrome Devtools
o-s-p.net SEO score
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 O-s-p.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 O-s-p.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.
o-s-p.net
Open Graph data is detected on the main page of O S P. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: