12.3 sec in total
876 ms
8.6 sec
2.8 sec
Click here to check amazing Eventapp content. Otherwise, check out these important facts you probably never knew about eventapp.co.za
Participate Technologies specialises in audience response technology. Basically put, we give your audience a voice. Our services RSVP & Ticketing Pages We offer bespoke, standalone RSVP pages for y...
Visit eventapp.co.zaWe analyzed Eventapp.co.za page load time and found that the first response time was 876 ms and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
eventapp.co.za performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value7.8 s
3/100
25%
Value12.9 s
2/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
876 ms
3809 ms
911 ms
65 ms
72 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 24% of them (16 requests) were addressed to the original Eventapp.co.za, 47% (32 requests) were made to Hb.wpmucdn.com and 19% (13 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Eventapp.co.za.
Page size can be reduced by 1.3 MB (71%)
1.8 MB
531.9 kB
In fact, the total size of Eventapp.co.za main page is 1.8 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. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 59.2 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 59.2 kB or 78% of the original size.
Potential reduce by 125.4 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. Obviously, Eventapp needs image optimization as it can save up to 125.4 kB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 97.4 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 97.4 kB or 51% of the original size.
Potential reduce by 998.1 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. Eventapp.co.za needs all CSS files to be minified and compressed as it can save up to 998.1 kB or 86% of the original size.
Number of requests can be reduced by 38 (73%)
52
14
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eventapp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
eventapp.co.za
876 ms
eventapp.co.za
3809 ms
wp-emoji-release.min.js
911 ms
css
65 ms
css
72 ms
ed26336a-fbc8-405b-8d2b-79fe70d8940c.css
280 ms
13a46d96-52e0-4f5c-9fde-0bce05916eea.css
268 ms
7dcb5209-660e-43a3-83ef-af20b08d0983.css
265 ms
e31d2c58-2682-4e88-8816-b38d242396e5.css
264 ms
ba932d74-3ae9-4761-b1b8-a903710755ce.css
265 ms
ca39c1ec-5012-469f-a573-f52a8abbb752.css
376 ms
d9b1bd9c-0c97-4433-bf94-8b16c4b94f7a.css
267 ms
0b38ac0c-2189-43ee-98f0-a61dd437d5e7.css
338 ms
b3730c50-c570-4211-9444-31d84409b1d2.css
337 ms
2fa43006-4f11-46ec-91bd-1d2559929e6a.css
278 ms
13cb3c0b-3e30-4cfd-9200-070ede38c556.css
275 ms
6c3f8914-6d14-40e1-99b6-9de0254413f8.css
274 ms
a9c8cf30-2254-41dd-adda-c67b98d4771b.css
601 ms
10e6e68f-6114-4dcc-a7a8-88a73bea2d72.css
589 ms
17120160-ab3b-42e4-ab5a-8268ca77740f.css
608 ms
f81a5add-efea-4e0d-b111-a0136c5df74f.js
599 ms
8a7f11e0-765a-47ba-92b4-a8957cd1bbea.js
607 ms
71fa7ac4-430d-4545-b2fd-d4d3cfc86b0e.js
599 ms
bc400156-5861-430d-9552-6ddf329a690b.js
598 ms
2ab93545-0ece-4e09-a48a-c52fbccd5371.js
763 ms
42f9dc7a-6dcd-4db1-940c-593ff6588cc1.js
782 ms
597a441e-4f5f-483c-940c-9c6c0bce6006.js
787 ms
75f6738e-340f-46a9-97e3-ea82b8e74740.js
785 ms
et-core-unified-tb-3635-6-16034631747413.min.css
1230 ms
et-core-unified-6-16034631747413.min.css
1248 ms
continually-embed.latest.min.js
711 ms
f9144f51-04d6-44d0-99e4-96ab53d29af2.js
623 ms
42ffc008-5a76-4efa-b39a-117661386bc5.js
599 ms
bf7ad569-eef4-4654-bf43-72c62c21e3e0.js
672 ms
a2f06e81-ce76-4fbc-b412-45b0fae19dcd.js
713 ms
85ac6b2b-85a2-40f4-aecf-6ce96c647974.js
708 ms
7d6c5a03-3499-4f1a-9b8e-c51e38d0b642.js
670 ms
a05a4d00-ffa8-4f26-a214-6815242ded15.js
680 ms
e5b42b88-e97d-4183-b3f7-9b1deeea6989.js
680 ms
464eae2c-1bb7-42cd-b3b6-1b4bf5159914.js
707 ms
analytics.js
86 ms
pt-logo_120x90.png
417 ms
PT_Isometric_1920x1200.jpg
2632 ms
Icon_page_01.png
762 ms
Icon_app_02.png
762 ms
PT_Home_iPad.png
2607 ms
PT-Map.png
3124 ms
MB-School.png
2616 ms
collect
372 ms
web-dev-24.png
1149 ms
web-dev-05.png
1149 ms
web-dev-06.png
1467 ms
mem8YaGs126MiZpBA-UFW50d.woff
270 ms
mem5YaGs126MiZpBA-UN_r8OXOhv.woff
272 ms
mem5YaGs126MiZpBA-UNirkOXOhv.woff
1022 ms
mem5YaGs126MiZpBA-UN7rgOXOhv.woff
1029 ms
mem5YaGs126MiZpBA-UN8rsOXOhv.woff
1033 ms
modules.ttf
1818 ms
S6u9w4BMUTPHh6UVSwaPHw.woff
840 ms
S6uyw4BMUTPHjxAwWA.woff
837 ms
KFOlCnqEu92Fr1MmEU9fChc-.woff
840 ms
KFOmCnqEu92Fr1Mu7GxM.woff
839 ms
KFOlCnqEu92Fr1MmSU5fChc-.woff
841 ms
KFOkCnqEu92Fr1MmgVxGIzQ.woff
1077 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
871 ms
KFOlCnqEu92Fr1MmYUtfChc-.woff
857 ms
analytics.js
854 ms
258 ms
eventapp.co.za 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
eventapp.co.za 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
eventapp.co.za 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eventapp.co.za 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 Eventapp.co.za 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.
eventapp.co.za
Open Graph description is not detected on the main page of Eventapp. 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: