2.1 sec in total
905 ms
1.2 sec
0 ms
Click here to check amazing Hortitimes content for South Korea. Otherwise, check out these important facts you probably never knew about hortitimes.com
과수, 채소, 화훼, 친환경 재배 농가, 취미원예 전문지
Visit hortitimes.comWe analyzed Hortitimes.com page load time and found that the first response time was 905 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
hortitimes.com performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value17.4 s
0/100
25%
Value16.2 s
0/100
10%
Value330 ms
75/100
30%
Value0.259
48/100
15%
Value15.8 s
6/100
10%
905 ms
239 ms
Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Hortitimes.com and no external sources were called. The less responsive or slowest element that took the longest time to load (905 ms) belongs to the original domain Hortitimes.com.
Page size can be reduced by 26.1 kB (82%)
31.9 kB
5.8 kB
In fact, the total size of Hortitimes.com main page is 31.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 31.2 kB which makes up the majority of the site volume.
Potential reduce by 258 B
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 258 B or 33% of the original size.
Potential reduce by 25.9 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 25.9 kB or 83% of the original size.
We found no issues to fix!
1
1
The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hortitimes. According to our analytics all requests are already optimized.
hortitimes.com
905 ms
cupid.js
239 ms
hortitimes.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
hortitimes.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hortitimes.com SEO score
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
KO
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hortitimes.com can be misinterpreted by Google and other search engines. Our service has detected that Korean 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 Hortitimes.com main page’s claimed encoding is . 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.
hortitimes.com
Open Graph description is not detected on the main page of Hortitimes. 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: