9.1 sec in total
122 ms
8.3 sec
679 ms
Click here to check amazing Perryvilla content. Otherwise, check out these important facts you probably never knew about perryvilla.net
Caribbean Magazine
Visit perryvilla.netWe analyzed Perryvilla.net page load time and found that the first response time was 122 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
perryvilla.net performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value6.9 s
6/100
25%
Value31.8 s
0/100
10%
Value56,550 ms
0/100
30%
Value0.068
96/100
15%
Value80.7 s
0/100
10%
122 ms
48 ms
140 ms
148 ms
153 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Perryvilla.net, 39% (40 requests) were made to Static.parastorage.com and 33% (34 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 2.6 MB (54%)
4.9 MB
2.2 MB
In fact, the total size of Perryvilla.net main page is 4.9 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. 80% 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 73 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 73 B or 27% of the original size.
Potential reduce by 55.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. Perryvilla images are well optimized though.
Potential reduce by 2.3 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 2.3 MB or 74% of the original size.
Potential reduce by 247.5 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. Perryvilla.net needs all CSS files to be minified and compressed as it can save up to 247.5 kB or 83% of the original size.
Number of requests can be reduced by 57 (61%)
94
37
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perryvilla. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
perryvilla.net
122 ms
photojournalist
48 ms
bt
140 ms
require.min.js
148 ms
main-r.min.js
153 ms
viewer.css
250 ms
ugc-viewer
83 ms
dynamicmodel
80 ms
da0f2d_089a743f2e83f1f79371769e1356ce2a_72.json.z
1491 ms
da0f2d_3432f93083698551333ed68b99ca6733_72.json.z
441 ms
ugc-viewer
73 ms
bt
138 ms
skins.min.js
385 ms
components.min.js
139 ms
utils.min.js
379 ms
core.min.js
385 ms
react-with-addons.min.js
115 ms
lodash.min.js
88 ms
TweenMax.min.js
369 ms
layout.min.js
136 ms
tpa.min.js
358 ms
fonts.min.js
369 ms
animations.min.js
358 ms
swfobject.min.js
346 ms
mousetrap.min.js
346 ms
tweenEngine.min.js
347 ms
DrawSVGPlugin.min.js
347 ms
react-dom.min.js
346 ms
ScrollToPlugin.min.js
348 ms
widgets.min.js
348 ms
experiment.js
350 ms
render.min.js
346 ms
wixappsCore.min.js
351 ms
wixappsBuilder.min.js
354 ms
zepto.min.js
348 ms
color.min.js
346 ms
react-dom-server.min.js
58 ms
bt
837 ms
bt
562 ms
dc.js
556 ms
da00086a27cc2c52ec7a11ec468c4d29.wix_mp
342 ms
shdtop.png
327 ms
css
323 ms
latin.css
319 ms
Honeycomb.html
336 ms
50503b14371f4daf4869fe9f06ee6c4b.png
519 ms
89b1d2497b29ccbb7d37be1ec6ef0052.png
133 ms
3ba48f6dde3eec5c30a46f1337500f50.wix_mp
522 ms
da0f2d_f5d0aeda72eb4721821b6020248e2125.jpg
520 ms
bt
210 ms
bt
202 ms
bt
201 ms
z-hy1PALECk
906 ms
jquery.min.js
151 ms
lodash.min.js
183 ms
paper-full.min.js
192 ms
utils.js
189 ms
app.proto.js
495 ms
wix.min.js
902 ms
style.min.css
441 ms
app.min.js
440 ms
__utm.gif
326 ms
soundmanager2-nodebug-jsmin.js
314 ms
o6rNQ4O3mMTvz3bHPzdNOw.ttf
366 ms
05b176f5-c622-4c35-af98-c0c056dd5b66.woff
311 ms
5t8vP9Hx2udzw372glmOxA.ttf
769 ms
da0f2d_f5d0aeda72eb4721821b6020248e2125.jpg
1719 ms
ugc-viewer
502 ms
ga-audiences
568 ms
www-embed-player-vfl-z2BtK.css
636 ms
www-embed-player.js
1147 ms
css
1024 ms
da0f2d_63514744b1b74fdca36cc81abdb9ddea.jpg
697 ms
da0f2d_c1d622ba1e384d208d28c17e14c6fb70.jpg
695 ms
da0f2d_2387a49bbe1648708e87f9eb5d7ccb7d.jpg
694 ms
da0f2d_f40ced8e241046c59d018a699dd1c956.jpg
692 ms
da0f2d_181a6cfe6c15444f94ff67d02b9dc874.jpg
1327 ms
da0f2d_8f607d596d904ac5a5d81fea56ae8fe0.jpg
1343 ms
da0f2d_e533ad4c1a4c497bac6d2c01adf839f8.jpg
1339 ms
da0f2d_95c4e5e80eee4acb898d2ae543f35f05.jpg
1330 ms
da0f2d_7ad0d2e620c1443592774a4ec7410b37.jpg
1328 ms
da0f2d_c586ccbb9427437bb973c8dc4704204d.jpg
1326 ms
da0f2d_a732513765734ac6aecbe2b2912a2017.jpg
1362 ms
da0f2d_4bf0c7b9ba6f45219f6d969939e188e6.jpg
1343 ms
da0f2d_05c34d87bac64c2f8bcfa8d487b992dd.jpg
1359 ms
da0f2d_8c2ae832a65e4e3c999b19a2b047a2c1.jpg
1357 ms
da0f2d_a1c1568fcc2a476b965d2b94491bb3bd.jpg
1343 ms
da0f2d_42f39d2918d04aaa9a0c59203ef55ce3.jpg
2401 ms
da0f2d_5cc99ef5052a4c3aab1ce8fdb58047df.jpg
2590 ms
da0f2d_1651ae7e271d4adabff677c64d811fc3.jpg
2589 ms
da0f2d_baf7269235954b159c63bebe4df3e08e.jpg
2404 ms
da0f2d_50fc835f2bfd4d5eb134b3d4cb335865.jpg
2596 ms
da0f2d_b5798ceb297445a5941f5cd2af551041.jpg
2596 ms
da0f2d_3f9b73f63baa48d4929ed5de8a42ea9d.jpg
2588 ms
da0f2d_94b7c59c1cab4eee9b47e1e65cb460e1.jpg
2588 ms
da0f2d_de54f069a2384acfbf8da2090f5a739d.jpg
4172 ms
da0f2d_3cff28c286fd4e508eff2d8749195e23.jpg
4123 ms
da0f2d_7b5ee842cacf488095681aaa39dbb1d5.jpg
4160 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
101 ms
ad_status.js
641 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
1231 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
1230 ms
perryvilla.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
perryvilla.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
perryvilla.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
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perryvilla.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Perryvilla.net 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.
perryvilla.net
Open Graph description is not detected on the main page of Perryvilla. 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: