14.1 sec in total
489 ms
12.8 sec
792 ms
Visit prometea.info now to see the best up-to-date Prometea content for Japan and also check out these interesting facts you probably never knew about prometea.info
高級賃貸マンションをお探しなら東京プロメティア。当店は、東京都内の賃貸マンションを路線や地域で検索できるサイトです。仲介手数料を最大無料キャンペーン中
Visit prometea.infoWe analyzed Prometea.info page load time and found that the first response time was 489 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
prometea.info performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value7.0 s
6/100
25%
Value10.3 s
8/100
10%
Value3,920 ms
1/100
30%
Value0.713
7/100
15%
Value26.2 s
0/100
10%
489 ms
1362 ms
333 ms
850 ms
364 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 92% of them (130 requests) were addressed to the original Prometea.info, 3% (4 requests) were made to Platform.twitter.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Prometea.info.
Page size can be reduced by 564.9 kB (15%)
3.7 MB
3.1 MB
In fact, the total size of Prometea.info main page is 3.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. 55% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 34.7 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 34.7 kB or 79% of the original size.
Potential reduce by 382.6 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, Prometea needs image optimization as it can save up to 382.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 109.6 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 109.6 kB or 66% of the original size.
Potential reduce by 37.9 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. Prometea.info needs all CSS files to be minified and compressed as it can save up to 37.9 kB or 84% of the original size.
Number of requests can be reduced by 28 (20%)
139
111
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prometea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
prometea.info
489 ms
www.prometea.info
1362 ms
import.css
333 ms
jquery.js
850 ms
common.js
364 ms
bxslider.js
750 ms
platform.js
118 ms
base.css
355 ms
layout.css
546 ms
system_extend.css
376 ms
bg_body_home.gif
176 ms
tel.png
782 ms
logo.png
709 ms
anav01.gif
350 ms
anav02.gif
355 ms
anav03.gif
383 ms
top_visual.jpg
1103 ms
tower.gif
708 ms
ic_arr.gif
709 ms
low.gif
782 ms
ic_loupe.gif
1034 ms
gnav01.gif
1047 ms
gnav02.gif
1055 ms
gnav03.gif
1064 ms
gnav04.gif
1085 ms
gnav05.gif
1397 ms
gnav06.gif
1395 ms
tnav01.gif
1392 ms
tnav02.gif
1415 ms
tnav03.gif
1447 ms
tnav04.gif
1452 ms
tnav05.gif
1758 ms
tnav06.gif
1762 ms
tnav07.gif
1769 ms
tnav08.gif
1766 ms
bg_main.gif
1791 ms
border_top2.gif
1813 ms
home_object_nav01.gif
2110 ms
home_object_nav02.gif
2113 ms
home_object_nav03.gif
2108 ms
home_object_nav04.gif
2133 ms
btn_other.gif
2130 ms
bg_homesearch.gif
2175 ms
article_1_3057.jpg
2811 ms
ic_p.gif
2464 ms
widgets.js
88 ms
article_1_3055.jpg
2962 ms
ga.js
36 ms
__utm.gif
33 ms
article_1_3048.jpg
2849 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
126 ms
syndication
112 ms
494054714690920450
195 ms
article_1_49461400467501.jpg
2536 ms
article_1_49451400467451.jpg
2820 ms
article_1_3044.jpg
2820 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
150 ms
DeSBaglG_normal.png
239 ms
article_1_3042.jpg
2964 ms
article_1_918_1444373919.jpg
2905 ms
article_1_49231400465835.jpg
2950 ms
article_1_49111400464746.jpg
3000 ms
article_1_49091400464598.jpg
3199 ms
jot
27 ms
article_1_49061400464451.jpg
3017 ms
article_1_599_1427450848.jpg
3841 ms
article_1_37691400395144.jpg
3479 ms
article_1_4451400466448.jpg
3573 ms
article_1_49131400465091.jpg
3753 ms
article_1_37801400395539.jpg
3862 ms
article_1_49341400466737.jpg
3484 ms
article_1_37651400394296.jpg
3984 ms
article_1_49021400464133.jpg
3753 ms
article_1_712_1377783919.jpg
4084 ms
article_1_52451400476972.jpg
4133 ms
article_1_48521400411502.jpg
4153 ms
article_1_48501400411429.jpg
4139 ms
article_1_48311400410258.jpg
4084 ms
article_1_48301400410178.jpg
4700 ms
article_1_26521420703497.jpg
4610 ms
article_1_31_1375966100.jpg
4671 ms
bg_main_shadow2.gif
4132 ms
home_search_bnr03.gif
4078 ms
home_search_bnr01.gif
4125 ms
home_search_bnr02.gif
4162 ms
home_newarrival_title.gif
4408 ms
ic_new.gif
4475 ms
bg_side_shadow.gif
4452 ms
side_prom_title.gif
4265 ms
side_prom_bg.gif
3977 ms
side_prom_st01.gif
3926 ms
side_prom_img.gif
4034 ms
side_prom_st02.gif
3937 ms
side_prom_st03.gif
3826 ms
side_rank_bg.png
3891 ms
bnr_tower2014.gif
3696 ms
bnr_fire2014.png
3690 ms
bg_side_shadow2.gif
3610 ms
side_pick_5.png
3572 ms
article_1_649_1445417289.jpg
3913 ms
article_1_7041441971294.png
4579 ms
article_1_2818_1376659810.jpg
3620 ms
article_1_45411400481050.jpg
3414 ms
article_1_240_1445418259.jpg
3044 ms
titlebar_side_tw.gif
2849 ms
btn_tweet.gif
3169 ms
bnr_facebook.gif
3287 ms
side_news_title.gif
3164 ms
bnr01.gif
3017 ms
bnr02.gif
2921 ms
bnr03.gif
2938 ms
realtor_latour.jpg
2982 ms
realtor_park_axis.jpg
2807 ms
realtor_apartments.jpg
2874 ms
realtor_park_habio.jpg
2815 ms
realtor_residia.jpg
2690 ms
realtor_conforia.jpg
2701 ms
realtor_castaria.jpg
2687 ms
realtor_belle_face.jpg
2637 ms
realtor_proud.jpg
2662 ms
realtor_pacific_residence.jpg
2656 ms
realtor_forecity.jpg
2693 ms
realtor_platinum_court.jpg
2705 ms
btn_finfo.gif
2687 ms
bg_slider.png
2636 ms
bg_footer.gif
2684 ms
ic_foot.gif
2679 ms
bg_copyright.gif
2580 ms
realtor_latour.jpg
2652 ms
realtor_park_axis.jpg
2611 ms
realtor_apartments.jpg
2654 ms
realtor_park_habio.jpg
2514 ms
realtor_residia.jpg
2516 ms
realtor_conforia.jpg
2570 ms
realtor_castaria.jpg
2641 ms
realtor_belle_face.jpg
2283 ms
realtor_proud.jpg
2239 ms
realtor_pacific_residence.jpg
2255 ms
btn_slider_left.png
2154 ms
btn_silder_right.png
2208 ms
prometea.info 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
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
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.
prometea.info 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
Missing source maps for large first-party JavaScript
prometea.info 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 doesn't use legible font sizes
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prometea.info can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Prometea.info 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.
prometea.info
Open Graph description is not detected on the main page of Prometea. 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: