17 sec in total
944 ms
15.5 sec
586 ms
Visit washington.jp now to see the best up-to-date Washington content for Japan and also check out these interesting facts you probably never knew about washington.jp
全国に18施設のホテルを展開している、ワシントンホテルプラザチェーン。ビジネス・観光の拠点に便利な立地で、選ばれ続けるビジネスホテル。
Visit washington.jpWe analyzed Washington.jp page load time and found that the first response time was 944 ms and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
washington.jp performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value8.4 s
2/100
25%
Value11.7 s
4/100
10%
Value1,070 ms
24/100
30%
Value0.482
17/100
15%
Value19.2 s
2/100
10%
944 ms
328 ms
338 ms
341 ms
342 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Washington.jp, 4% (4 requests) were made to Tg.socdm.com and 3% (3 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (12.8 sec) relates to the external source Www4.489pro.com.
Page size can be reduced by 390.9 kB (21%)
1.9 MB
1.5 MB
In fact, the total size of Washington.jp main page is 1.9 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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 46.8 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 7.8 kB, which is 14% 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 46.8 kB or 81% of the original size.
Potential reduce by 245.5 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. Obviously, Washington needs image optimization as it can save up to 245.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 82.7 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 82.7 kB or 43% of the original size.
Potential reduce by 16.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. Washington.jp needs all CSS files to be minified and compressed as it can save up to 16.0 kB or 33% of the original size.
Number of requests can be reduced by 49 (52%)
95
46
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washington. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
washington.jp
944 ms
font-awesome.min.css
328 ms
jquery-ui.min.css
338 ms
jquery-ui.theme.min.css
341 ms
drawer.min.css
342 ms
default.css
348 ms
common.css
526 ms
components.css
654 ms
homepage.css
676 ms
slick.css
677 ms
jquery-1.9.1.min.js
1032 ms
analytics_was.js
686 ms
common.js
851 ms
search.js
978 ms
search_net_point.js
1012 ms
jquery-ui.min.js
1226 ms
jquery.ui.datepicker-ja.min.js
1010 ms
jquery.heightLine.js
1226 ms
iscroll-min.js
1307 ms
jquery.drawer.min.js
1411 ms
jquery.cookie.js
1412 ms
slick.min.js
1413 ms
jquery.rwdImageMaps.min.js
1512 ms
map_list.js
1517 ms
homepage.js
1654 ms
ypro_stock_fn.js
1683 ms
analytics.js
24 ms
logo_wa.png
678 ms
logo_rb.png
679 ms
logo_np.png
806 ms
ic_name.png
809 ms
bn_sakae23.2.5_pc.jpg
1422 ms
bn_sakae23.2.5_sp.jpg
1290 ms
ic_bestrate_l.png
1005 ms
bn_dp.jpg
1372 ms
bn_group_pc.jpg
1619 ms
bn_dp_s.jpg
1327 ms
bn_group_sp.jpg
1517 ms
img_jmap-sp.png
1964 ms
img_jmap_wide.png
1978 ms
bn_mor.jpg
2248 ms
img_omo.jpg
2263 ms
bn_roo.jpg
2241 ms
logo_gr_wa.png
2075 ms
logo_gr_rb.png
2315 ms
logo_gr_co.png
2317 ms
btn_pgtop.png
2413 ms
gtm.js
71 ms
bg_gr_head.png
2577 ms
ic_list_gr.png
2572 ms
ic_logo.png
2591 ms
ic_small_r.png
2638 ms
ic_smo.png
2646 ms
btn_sq_r.png
2733 ms
collect
85 ms
fontawesome-webfont.woff
3258 ms
mv_1.jpg
3753 ms
ytag.js
741 ms
collect
24 ms
js
53 ms
ga-audiences
31 ms
ic_slash.png
2688 ms
st_selling.png
2621 ms
washington.jp
3057 ms
st_group.png
2723 ms
json
12825 ms
ypro_stocksearch_api.asp
1381 ms
bn_net_s.png
2944 ms
bn_net_ca_s_upper.png
2996 ms
bn_line_s_lower.png
2948 ms
so.js
1078 ms
bn_rcard_to_net.jpg
3587 ms
img_jmap_1.png
3409 ms
img_lmap_1.png
3418 ms
img_jmap_2.png
3503 ms
img_lmap_2.png
3524 ms
img_jmap_3.png
3609 ms
img_lmap_3.png
3471 ms
img_jmap_4.png
3420 ms
img_lmap_4.png
3595 ms
img_jmap_5.png
3603 ms
img_lmap_5.png
3518 ms
img_jmap_6.png
3667 ms
js
692 ms
img_lmap_6.png
3459 ms
v3
626 ms
sosync
184 ms
L21rdC82ODEvcGlkLzQzNzc1MDA4L3QvMA
8 ms
41 ms
pixel
42 ms
v2
6 ms
sync
702 ms
sync
43 ms
16 ms
pixel
16 ms
pixel
15 ms
sync
800 ms
sd
29 ms
Pug
18 ms
hs
828 ms
um
45 ms
tap.php
25 ms
washington.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
Form elements do not have associated labels
Links do not have a discernible name
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
washington.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
washington.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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Washington.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 Washington.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.
washington.jp
Open Graph description is not detected on the main page of Washington. 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: