13.3 sec in total
580 ms
12.4 sec
274 ms
Click here to check amazing Publishme content for New Zealand. Otherwise, check out these important facts you probably never knew about publishme.co.nz
PublishMe self-publishing and book printing services, including; cover design, editing, proofreading. Based in New Plymouth, New Zealand
Visit publishme.co.nzWe analyzed Publishme.co.nz page load time and found that the first response time was 580 ms and then it took 12.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
publishme.co.nz performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value15.5 s
0/100
25%
Value13.0 s
2/100
10%
Value150 ms
95/100
30%
Value0.11
87/100
15%
Value11.8 s
17/100
10%
580 ms
1716 ms
362 ms
571 ms
386 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 73% of them (82 requests) were addressed to the original Publishme.co.nz, 6% (7 requests) were made to Fonts.googleapis.com and 6% (7 requests) were made to New.publishme.co.nz. The less responsive or slowest element that took the longest time to load (6.1 sec) relates to the external source New.publishme.co.nz.
Page size can be reduced by 2.4 MB (56%)
4.2 MB
1.9 MB
In fact, the total size of Publishme.co.nz main page is 4.2 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. 65% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 71.5 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 71.5 kB or 82% of the original size.
Potential reduce by 44.9 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. Publishme images are well optimized though.
Potential reduce by 1.2 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.2 MB or 70% of the original size.
Potential reduce by 1.1 MB
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. Publishme.co.nz needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.
Number of requests can be reduced by 68 (67%)
102
34
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Publishme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
publishme.co.nz
580 ms
1716 ms
wp-emoji-release.min.js
362 ms
um.min.css
571 ms
um-recaptcha.css
386 ms
styles.css
384 ms
settings.css
770 ms
css
32 ms
css
59 ms
css
56 ms
settings.css
1774 ms
frontend-forms.css
548 ms
style.css
578 ms
jquery-ui-1.9.1.custom.css
579 ms
pagenavi-css.css
735 ms
css
49 ms
reset.css
756 ms
text.css
757 ms
960.css
763 ms
superfish.css
923 ms
font-awesome.css
946 ms
style.css
1136 ms
custom_style.css
952 ms
responsive.css
955 ms
fluid.css
1110 ms
style.css
1134 ms
js_composer.min.css
1732 ms
jquery.js
1534 ms
jquery-migrate.min.js
1300 ms
jquery.form.min.js
1321 ms
scripts.js
1323 ms
lightbox.js
1489 ms
jquery.themepunch.tools.min.js
1710 ms
jquery.themepunch.essential.min.js
1706 ms
jquery.themepunch.revolution.min.js
1679 ms
js
22 ms
frontend-form.js
1723 ms
core.min.js
1868 ms
datepicker.min.js
1896 ms
plupload.full.min.js
2092 ms
handlers.min.js
1912 ms
jquery-ui-timepicker-addon.js
1921 ms
css
39 ms
css
39 ms
css
39 ms
api.js
46 ms
upload.js
1791 ms
wpcf7.js
1706 ms
um.min.js
2101 ms
conditional-logic.js
1729 ms
subscriptions.js
1572 ms
widget.min.js
1569 ms
position.min.js
1675 ms
menu.min.js
1715 ms
autocomplete.min.js
1565 ms
suggest.min.js
1555 ms
mouse.min.js
1576 ms
slider.min.js
1677 ms
superfish.combined.js
1716 ms
script.js
1566 ms
selectnav.min.js
1550 ms
selectnav-options.js
1569 ms
comment-reply.min.js
1668 ms
js_composer_front.js
1558 ms
style.css
1535 ms
waypoints.min.js
1625 ms
analytics.js
16 ms
2.png
631 ms
Untitled-1.png
761 ms
PMLOGO_180x150.png
229 ms
key.png
229 ms
profle.png
228 ms
I-want-to-be-a-writer1.jpg
799 ms
iStock_000012689423Large.png
758 ms
1.png
419 ms
Mixed_covers1600.jpg
2237 ms
3.png
872 ms
4.png
1000 ms
5.png
2017 ms
5.png
419 ms
calendar-85x85.png
607 ms
compose-85x85.png
609 ms
scissors-85x85.png
800 ms
brush-pencil-85x85.png
802 ms
bookshelf-85x85.png
942 ms
money.png
947 ms
check.png
987 ms
news.png
987 ms
phone.png
6009 ms
mail.png
6062 ms
location.png
813 ms
collect
26 ms
collect
162 ms
heading_underline.png
907 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
24 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
24 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
25 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
25 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
25 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
24 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
24 ms
recaptcha__en.js
125 ms
revolution.extension.slideanims.min.js
953 ms
revolution.extension.layeranimation.min.js
961 ms
revolution.extension.kenburn.min.js
993 ms
revolution.extension.navigation.min.js
997 ms
revolution.extension.parallax.min.js
1001 ms
auto-arrows.png
1135 ms
revicons.woff
191 ms
common.js
4 ms
util.js
20 ms
stats.js
20 ms
AuthenticationService.Authenticate
258 ms
publishme.co.nz accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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.
publishme.co.nz 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
publishme.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publishme.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Publishme.co.nz 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.
publishme.co.nz
Open Graph description is not detected on the main page of Publishme. 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: