2.1 sec in total
163 ms
1.8 sec
177 ms
Click here to check amazing Prezly content for Mexico. Otherwise, check out these important facts you probably never knew about prezly.com
Use Prezly to publish stunning multimedia stories and distribute them to your top contacts. No code required.
Visit prezly.comWe analyzed Prezly.com page load time and found that the first response time was 163 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
prezly.com performance score
name
value
score
weighting
Value2.2 s
77/100
10%
Value9.7 s
0/100
25%
Value6.3 s
41/100
10%
Value1,820 ms
9/100
30%
Value0
100/100
15%
Value14.0 s
10/100
10%
163 ms
452 ms
171 ms
67 ms
383 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 21% of them (11 requests) were addressed to the original Prezly.com, 6% (3 requests) were made to Pixel.prfct.co and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (452 ms) belongs to the original domain Prezly.com.
Page size can be reduced by 298.8 kB (50%)
599.4 kB
300.7 kB
In fact, the total size of Prezly.com main page is 599.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 317.1 kB which makes up the majority of the site volume.
Potential reduce by 23.4 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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.4 kB or 76% of the original size.
Potential reduce by 5.2 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. Prezly images are well optimized though.
Potential reduce by 140.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 140.9 kB or 44% of the original size.
Potential reduce by 129.3 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. Prezly.com needs all CSS files to be minified and compressed as it can save up to 129.3 kB or 82% of the original size.
Number of requests can be reduced by 33 (75%)
44
11
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prezly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
prezly.com
163 ms
www.prezly.com
452 ms
prezly.css
171 ms
css
67 ms
bundle.js
383 ms
prezly.js
331 ms
conversion_async.js
55 ms
oct.js
125 ms
conversion.js
55 ms
j.php
88 ms
analytics.min.js
226 ms
logo.png
95 ms
home_crm_ipad.jpg
305 ms
avatar_evelinederidder_lg.jpg
214 ms
avatar_kimdaenen_lg.jpg
216 ms
ajax-loader.gif
305 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
85 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
85 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
114 ms
icomoon.woff
393 ms
v.gif
9 ms
api.min.js
116 ms
adsct
174 ms
track.js
129 ms
fbevents.js
352 ms
analytics.js
146 ms
t93knr8n
168 ms
mixpanel-2-latest.min.js
76 ms
raven.min.js
145 ms
52c008f986c4d6863e000027.js
167 ms
jquery.min.js
164 ms
58 ms
149 ms
106 ms
94 ms
98 ms
linkid.js
32 ms
intercom.c5a1eeb5.js
90 ms
collect
34 ms
collect
153 ms
tagjs
3 ms
106 ms
Pug
146 ms
adsct
93 ms
echo.515e8809.js
34 ms
pixel
82 ms
54 ms
cb
38 ms
sd
20 ms
tap.php
24 ms
cb
6 ms
ncm
8 ms
cb
7 ms
prezly.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
prezly.com 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
Missing source maps for large first-party JavaScript
prezly.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prezly.com 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 Prezly.com 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.
prezly.com
Open Graph description is not detected on the main page of Prezly. 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: