8.8 sec in total
1.7 sec
7 sec
128 ms
Welcome to tolinen.com homepage info - get ready to check Tolinen best content for Japan right away, or after learning these important things about tolinen.com
テーオーリネンサプライは、長年ラグジュアリーホテルを中心にリネンサプライとクリーニング(ランドリー/ドライクリーニング/プレス)のサービスをご提供しております。クオリティを望まれているお客様に上質なサービスをご提供いたします。
Visit tolinen.comWe analyzed Tolinen.com page load time and found that the first response time was 1.7 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
tolinen.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value10.1 s
0/100
25%
Value9.4 s
12/100
10%
Value350 ms
73/100
30%
Value0.001
100/100
15%
Value4.9 s
78/100
10%
1656 ms
28 ms
495 ms
504 ms
25 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 86% of them (44 requests) were addressed to the original Tolinen.com, 4% (2 requests) were made to Maxcdn.bootstrapcdn.com and 4% (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 Tolinen.com.
Page size can be reduced by 292.2 kB (6%)
4.7 MB
4.4 MB
In fact, the total size of Tolinen.com main page is 4.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. 45% of websites need less resources to load. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 17.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 17.0 kB or 77% of the original size.
Potential reduce by 9.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. Tolinen images are well optimized though.
Potential reduce by 223.0 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 223.0 kB or 63% of the original size.
Potential reduce by 43.2 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. Tolinen.com needs all CSS files to be minified and compressed as it can save up to 43.2 kB or 79% of the original size.
Number of requests can be reduced by 30 (65%)
46
16
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tolinen. 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 from 11 to 1 for CSS and as a result speed up the page load time.
www.tolinen.com
1656 ms
jquery.min.js
28 ms
retina.js
495 ms
style.css
504 ms
css
25 ms
font-awesome.min.css
6 ms
font.css
332 ms
jquery.sidr.dark.css
382 ms
jquery.sidr.min.js
530 ms
top.css
470 ms
jquery.bxslider.min.js
990 ms
jquery.bxslider.css
546 ms
slider.js
629 ms
nextgen_gallery_related_images.css
506 ms
styles.css
518 ms
styles.css
547 ms
jquery.fancybox-1.3.4.css
562 ms
ajax.js
639 ms
jquery.js
1160 ms
jquery-migrate.min.js
684 ms
persist.js
880 ms
store.js
725 ms
ngg_store.js
796 ms
lightbox_context.js
856 ms
jquery.form.min.js
738 ms
scripts.js
809 ms
scripts.js
853 ms
common.js
871 ms
jquery.easing-1.3.pack.js
896 ms
jquery.fancybox-1.3.4.pack.js
908 ms
nextgen_fancybox_init.js
967 ms
analytics.js
17 ms
wp-emoji-release.min.js
370 ms
collect
12 ms
otani_lpgo.svg
482 ms
otani_lpgo.png
175 ms
01.jpg
494 ms
02.jpg
1655 ms
03.jpg
507 ms
04.jpg
3316 ms
05.jpg
673 ms
06.jpg
1923 ms
07.jpg
822 ms
08.jpg
1508 ms
TOC.png
841 ms
TOC.svg
990 ms
bx_loader.gif
1727 ms
controls.png
1855 ms
iU65JP9acQHPDLkdalCF7u921tOcMok2fHawGmtxikA.ttf
11 ms
fontawesome-webfont.woff
10 ms
NotoSans-Regular.woff
1637 ms
tolinen.com 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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.
tolinen.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tolinen.com SEO score
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 Tolinen.com 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 Tolinen.com 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.
tolinen.com
Open Graph description is not detected on the main page of Tolinen. 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: