12.1 sec in total
1.3 sec
8.7 sec
2.1 sec
Click here to check amazing PROST J content for South Korea. Otherwise, check out these important facts you probably never knew about prostj.com
모던하고 시크한 스타일, 프렌치한 감성 프로스트제이
Visit prostj.comWe analyzed Prostj.com page load time and found that the first response time was 1.3 sec and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
prostj.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value15.8 s
0/100
25%
Value24.1 s
0/100
10%
Value4,220 ms
1/100
30%
Value0.627
9/100
15%
Value60.4 s
0/100
10%
1324 ms
386 ms
24 ms
37 ms
30 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 85% of them (110 requests) were addressed to the original Prostj.com, 3% (4 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Img.echosting.cafe24.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Prostj.com.
Page size can be reduced by 617.7 kB (8%)
8.1 MB
7.5 MB
In fact, the total size of Prostj.com main page is 8.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.9 MB which makes up the majority of the site volume.
Potential reduce by 101.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 101.0 kB or 90% of the original size.
Potential reduce by 493.4 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. PROST J images are well optimized though.
Potential reduce by 22.8 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 22.8 kB or 29% of the original size.
Potential reduce by 542 B
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. Prostj.com needs all CSS files to be minified and compressed as it can save up to 542 B or 54% of the original size.
Number of requests can be reduced by 12 (10%)
122
110
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROST J. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
prostj.com
1324 ms
common.js
386 ms
css
24 ms
css
37 ms
jquery.min.js
30 ms
jquery.min.js
41 ms
cid.generate.js
426 ms
wcslog.js
19 ms
optimizer.php
584 ms
ld.js
24 ms
optimizer.php
1182 ms
logo_cafe24.png
397 ms
right_banner_02.jpg
284 ms
right_banner_03.jpg
282 ms
main_img_01.jpg
2247 ms
main_img_02.jpg
2521 ms
main_img_03.jpg
2336 ms
main_img_04.jpg
2538 ms
prostj_2737.jpg
1187 ms
prostj_1433.jpg
1303 ms
custom_8.gif
1385 ms
prostj_2735.jpg
1689 ms
prostj_2130.jpg
1977 ms
prostj_2724.jpg
2074 ms
prostj_2738.jpg
2372 ms
prostj_2731.jpg
2458 ms
prostj_2710.jpg
2437 ms
prostj_2732.jpg
2528 ms
prostj_2693.jpg
2569 ms
prostj_2053.jpg
2629 ms
prostj_2733.jpg
2841 ms
prostj_2729.jpg
2904 ms
prostj_2725.jpg
2914 ms
prostj_2726.jpg
2728 ms
prostj_1922.jpg
2962 ms
prostj_1361.jpg
2821 ms
prostj_2705.jpg
2924 ms
prostj_2706.jpg
3205 ms
prostj_2714.jpg
3223 ms
prostj_1871.jpg
3289 ms
prostj_2681.jpg
3106 ms
custom_9.gif
3118 ms
prostj_1401.jpg
3355 ms
prostj_2131.jpg
3496 ms
prostj_2723.jpg
3314 ms
txt_progress.gif
483 ms
img_loading.gif
785 ms
prostj_2722.jpg
3394 ms
m
758 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
26 ms
MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf
118 ms
Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf
119 ms
b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf
118 ms
NanumGothic.woff
5864 ms
event
19 ms
prostj_2728.jpg
3220 ms
prostj_2719.jpg
3238 ms
event
358 ms
weblog.js
630 ms
popup_14.html
2602 ms
SubCategory
2330 ms
prostj_2713.jpg
2030 ms
prostj_2711.jpg
1838 ms
prostj_2715.jpg
1948 ms
prostj_2704.jpg
1865 ms
prostj_2702.jpg
1580 ms
prostj_1327.jpg
1539 ms
prostj_2685.jpg
1569 ms
prostj_2697.jpg
1648 ms
prostj_2688.jpg
1783 ms
prostj_2381.jpg
1672 ms
prostj_1948.jpg
1687 ms
prostj_2698.jpg
1776 ms
prostj_2676.jpg
1679 ms
prostj_2687.jpg
1665 ms
prostj_2675.jpg
1597 ms
prostj_2679.jpg
1845 ms
prostj_2692.jpg
1599 ms
prostj_2680.jpg
1628 ms
prostj_2669.jpg
1667 ms
prostj_2614.jpg
1852 ms
prostj_1425.jpg
1585 ms
prostj_2491.jpg
1617 ms
prostj_2010.jpg
1581 ms
prostj_2446.jpg
1657 ms
prostj_2670.jpg
1600 ms
prostj_2672.jpg
1614 ms
custom_11.gif
1623 ms
prostj_2666.jpg
1613 ms
prostj_1244.jpg
1583 ms
prostj_2484.jpg
1586 ms
prostj_2667.jpg
1615 ms
prostj_2664.jpg
1558 ms
optimizer.php
1595 ms
optimizer.php
1579 ms
prostj_2660.jpg
1570 ms
prostj_2126.jpg
1611 ms
prostj_2658.jpg
1556 ms
prostj_2609.jpg
1710 ms
prostj_2656.jpg
1569 ms
prostj_2657.jpg
1485 ms
prostj_2652.jpg
1507 ms
prostj_2651.jpg
1465 ms
prostj_718.jpg
1569 ms
prostj_2644.jpg
1484 ms
prostj_2647.jpg
1499 ms
prostj_2639.jpg
1464 ms
prostj_2645.jpg
1707 ms
prostj_2637.jpg
1524 ms
prostj_2641.jpg
1484 ms
prostj_2638.jpg
1496 ms
prostj_2633.jpg
1453 ms
prostj_2628.jpg
1522 ms
prostj_2629.jpg
1481 ms
prostj_2538.jpg
1424 ms
prostj_2068.jpg
1535 ms
prostj_2083.jpg
1493 ms
prostj_2625.jpg
1471 ms
prostj_1339.jpg
1455 ms
prostj_2624.jpg
1426 ms
prostj_2619.jpg
1431 ms
prostj_1567.jpg
1409 ms
prostj_2612.jpg
1628 ms
prostj_2622.jpg
1441 ms
prostj_2618.jpg
1387 ms
prostj_2617.jpg
1418 ms
seasonsale.jpg
1579 ms
m
464 ms
dis.aspx
358 ms
prostj.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
prostj.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prostj.com 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
KO
KO
EUC-KR
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prostj.com can be misinterpreted by Google and other search engines. Our service has detected that Korean is used on the page, and it matches the claimed language. Our system also found out that Prostj.com main page’s claimed encoding is euc-kr. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
prostj.com
Open Graph description is not detected on the main page of PROST J. 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: