728 ms in total
81 ms
578 ms
69 ms
Click here to check amazing Horizon Pg content. Otherwise, check out these important facts you probably never knew about horizonpg.net
Horizon Publishing Group a place where stories come to life, publishing books and ebooks.
Visit horizonpg.netWe analyzed Horizonpg.net page load time and found that the first response time was 81 ms and then it took 647 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
horizonpg.net performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.9 s
29/100
25%
Value14.4 s
1/100
10%
Value4,990 ms
0/100
30%
Value0.291
41/100
15%
Value18.2 s
3/100
10%
81 ms
62 ms
99 ms
45 ms
51 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Horizonpg.net, 72% (28 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (337 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.0 MB (76%)
2.6 MB
615.7 kB
In fact, the total size of Horizonpg.net main page is 2.6 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. 75% 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. Javascripts take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 73.6 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 73.6 kB or 83% of the original size.
Potential reduce by 1.9 MB
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 1.9 MB or 76% of the original size.
Potential reduce by 5.8 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. Horizonpg.net needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.
Number of requests can be reduced by 27 (73%)
37
10
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Horizon Pg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and as a result speed up the page load time.
horizonpg.net
81 ms
www.horizonpg.net
62 ms
bt
99 ms
require.min.js
45 ms
main-r.min.js
51 ms
viewer.css
50 ms
dynamicmodel
29 ms
b8d748_33e42dac8af1fdf0cc119cdec487c823_1447.json.z
337 ms
b8d748_7d42dca86f849ed4ea151a530b178969_1447.json.z
301 ms
ugc-viewer
111 ms
bt
116 ms
skins.min.js
213 ms
components.min.js
112 ms
utils.min.js
52 ms
core.min.js
105 ms
react-with-addons.min.js
51 ms
lodash.min.js
35 ms
TweenMax.min.js
103 ms
layout.min.js
110 ms
tpa.min.js
102 ms
fonts.min.js
103 ms
animations.min.js
105 ms
swfobject.min.js
103 ms
mousetrap.min.js
103 ms
tweenEngine.min.js
104 ms
DrawSVGPlugin.min.js
104 ms
react-dom.min.js
103 ms
ScrollToPlugin.min.js
104 ms
widgets.min.js
106 ms
experiment.js
104 ms
render.min.js
105 ms
wixappsCore.min.js
107 ms
wixappsBuilder.min.js
106 ms
zepto.min.js
106 ms
color.min.js
106 ms
bt
59 ms
react-dom-server.min.js
43 ms
dc.js
76 ms
bt
79 ms
horizonpg.net 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
<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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
horizonpg.net 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
horizonpg.net 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Horizonpg.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 Horizonpg.net 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.
horizonpg.net
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: