Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Thorlabs, Inc. - Your Source for Fiber Optics, Laser Diodes, Optical Instrumentation and Polarization Measurement & Control | Search engines recommend title length of around 50-60 characters. The length of this title is 123. |
| Load time | 3.1835 seconds on average | Load speed is a concern and should be improved if and when possible. |
| Alexa global | 627 633, as last updated | According to Alexa, the website's popularity is not exactly high. Take this rank with a healthy pinch of salt. |
| Total links on homepage | We found 91 links | This is a normal amount of links. |
| Page HTML size | 21.4KB | How do we put this... improvement is quite necessary. Load speed is a very important factor in so many ways! |
| Website server | Server appears to be online. The IP address for the server is 149.126.72.201. | It's unfortunate, but despite our best attempts, we failed to gather enough data to provide a meaningful insight at this time. |
What, all that information was not enough? You want... more? Right, then. You asked for it.
With over 4 million websites indexed (which can seem as a lot, or very little, depending on your point of view), Alexa is perhaps the oldest and certainly the best known ranking system, deservedly or not. The Alexa Global and Local ranks of a website are based on an approximate amount of visitors a given website receives. The more visitors, the higher the rank. The Alexa rank, be it Local or Global, should be taken with a pinch of salt. After all, visitor count is by far not the simple measure of a website's success it's made out to be. For example, a gardening website is never going to be as popular as a movie review website. It does not mean it's not popular within it's niche.
Similarly to how a hard drive or a modern SSD device holds your files, a server holds all the files the website needs to operate. To load a webpage, your browser needs to contact the said server and request files - strings of code that make up the website into what it is, including images, text and database entries. Each physical server has a unique IP address that is used by the browser to contact it.
Let's see what technical information we've managed to gather:
| Header in detail |
|---|
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Content-Type: text/html;charset=UTF-8
Content-Language: ja-JP
Server: Microsoft-IIS/8.5
Set-Cookie: CFID=13537573; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; HttpOnly
Set-Cookie: CFTOKEN=e4986c7318d45629-517E7BD1-DC01-F43C-2E612F2C5516D501; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; HttpOnly
Set-Cookie: LOADCURRENCY=JPY; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCURRENCYSYMBOL=%C2%A5; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCURRENCY=JPY; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCURRENCYSYMBOL=%C2%A5; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCOUNTRY=JP; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCOUNTRY2=JAPAN; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LANGUAGE=JAPANESE; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LANGABBR=JP; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LANGCSS=JPSite%2Ecss; Expires=Fri, 17-May-2047 16:45:36 GMT; Path=/; Secure; HttpOnly
Set-Cookie: LOADCOUNTRY=DE; Path=/
Set-Cookie: LOADCOUNTRY2=Germany; Path=/
Set-Cookie: LOADCURRENCY=JPY; Path=/
Set-Cookie: LOADCURRENCYSYMBOL=%C2%A5; Path=/
Set-Cookie: TEMPLOCAL=Japanese; Path=/
Set-Cookie: ROITRACK=1; Path=/; Secure; HttpOnly
Set-Cookie: EUCOOKIENOTE=Yes; Path=/
Strict-Transport-Security: max-age=86400
X-UA-Compatible: IE=edge
Date: Wed, 24 May 2017 16:45:36 GMT
Set-Cookie: visid_incap_1093891=r8LiwDYxRi25l1yNka7I0Ze4JVkAAAAAQUIPAAAAAACz8FXKG3/crldSRjHiQR0h; expires=Thu, 24 May 2018 13:16:19 GMT; path=/; Domain=.thorlabs.co.jp
Set-Cookie: nlbi_1093891=zOM2AA9x5mP4RPc3+IjQ/wAAAABysKOWvN5kqQ++UgTpCwp8; path=/; Domain=.thorlabs.co.jp
Set-Cookie: incap_ses_459_1093891=HqW2OhTsqFWMufbyfrJeBpe4JVkAAAAAhiQk/wTtwpodniUEmRRFIg==; path=/; Domain=.thorlabs.co.jp
Set-Cookie: ___utmvmvEuFYvBB=copMwgthROC; path=/; Max-Age=900
Set-Cookie: ___utmvavEuFYvBB=dHgSvtG; path=/; Max-Age=900
Set-Cookie: ___utmvbvEuFYvBB=zZE
XFxOEalj: qtx; path=/; Max-Age=900
X-Iinfo: 3-82447888-82447893 NNNN CT(257 524 0) RT(1495644310208 42) q(0 0 8 -1) r(12 12) U12
X-CDN: Incapsula |
| WHOIS information |
|---|
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ] Domain Information: a. [Domain Name] THORLABS.CO.JP g. [Organization] Thorlabs Japan Inc. l. [Organization Type] Company m. [Administrative Contact] YY13882JP n. [Technical Contact] YY13882JP p. [Name Server] ns1.jp-domains.jp p. [Name Server] ns2.jp-domains.jp p. [Name Server] ns3.jp-domains.jp p. [Name Server] ns4.jp-domains.jp s. [Signing Key] [State] Connected (2017/09/30) [Registered Date] 2002/09/30 [Connected Date] 2002/10/01 [Last Update] 2017/06/08 19:20:48 (JST) |
A good domain address is usually one that is easy to spell, resulting in the smallest amount of mistypes possible. Still, such a thing inevitably happens. Here is a list with the most frequent 1782 mistypes, associated with thorlabs.co.jp:
If you are curious about what TLD extensions could also match the domain name of thorlabs.co.jp well, we have prepared an extensive list for you to look through:
We are glad you have finished this report. Hopefully, you found what you were looking for. In case you need more information to compare, here is a list of some other detailed overviews we have prepared: