4.5 sec in total
602 ms
3.3 sec
646 ms
Click here to check amazing RCC content for Egypt. Otherwise, check out these important facts you probably never knew about rcc.eg
Visit rcc.egWe analyzed Rcc.eg page load time and found that the first response time was 602 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rcc.eg performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value32.4 s
0/100
25%
Value11.8 s
4/100
10%
Value590 ms
50/100
30%
Value0.35
31/100
15%
Value25.4 s
0/100
10%
602 ms
25 ms
38 ms
394 ms
260 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 43% of them (50 requests) were addressed to the original Rcc.eg, 21% (25 requests) were made to Maps.googleapis.com and 9% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Rcc.eg.
Page size can be reduced by 1.4 MB (53%)
2.6 MB
1.2 MB
In fact, the total size of Rcc.eg 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 29.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 3.7 kB, which is 11% 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 29.4 kB or 83% of the original size.
Potential reduce by 59.1 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. RCC images are well optimized though.
Potential reduce by 873.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 873.4 kB or 69% of the original size.
Potential reduce by 410.4 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. Rcc.eg needs all CSS files to be minified and compressed as it can save up to 410.4 kB or 85% of the original size.
Number of requests can be reduced by 64 (62%)
104
40
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RCC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
rcc.eg
602 ms
css
25 ms
css
38 ms
foundation.css
394 ms
design.css
260 ms
jquery.js
431 ms
jquery.js
472 ms
jquery.easing.1.3.js
302 ms
jquery.cycle2.all.js
575 ms
modernizr.foundation.js
446 ms
jquery.fancybox.js
628 ms
jquery.fancybox.css
579 ms
jquery.fancybox-buttons.css
592 ms
jquery.fancybox-buttons.js
619 ms
jquery.fancybox-thumbs.css
628 ms
jquery.fancybox-thumbs.js
739 ms
jquery.fancybox-media.js
736 ms
style.css
778 ms
owl.carousel.js
949 ms
owl.carousel.css
789 ms
owl.theme.css
805 ms
jquery.sticky.js
699 ms
smoothscroll.js
702 ms
jquery.tweet.js
740 ms
contact.js
752 ms
app.js
797 ms
foundation.min.js
978 ms
script.js
887 ms
nav.css
857 ms
font-awesome.css
953 ms
jquery.tweet.css
892 ms
animate.css
1063 ms
shadows.css
993 ms
contact.css
1013 ms
logo.png
417 ms
11290.jpg
651 ms
21739.jpg
540 ms
3727.jpg
540 ms
autodesk292.png
271 ms
Apple1115.png
265 ms
cms1005.png
435 ms
adobe1511.png
538 ms
Final%207.jpg
741 ms
Final%20x.jpg
706 ms
Motion%204.jpg
720 ms
Motion.jpg
774 ms
Soundtrack.jpg
761 ms
logo_menu.png
880 ms
border_bg_dark.png
881 ms
border_bg_light.png
890 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
27 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
28 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
29 ms
ms
174 ms
icon_top.png
874 ms
BzdOPh9mDOc
203 ms
MG9KbUZFchDs94Tbv9U-paCWcynf_cDxXwCLxiixG1c.ttf
123 ms
uDssvmXgp7Nj3i336k_dSonF5uFdDttMLvmWuJdhhgs.ttf
123 ms
-91TwiFzqeL1F7Kh91APwYnF5uFdDttMLvmWuJdhhgs.ttf
134 ms
fontawesome-webfont.woff
992 ms
embed
460 ms
www-embed-player-vflfNyN_r.css
20 ms
www-embed-player.js
43 ms
base.js
68 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
44 ms
ad_status.js
87 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
63 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg
50 ms
css
74 ms
js
96 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
67 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
5 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
8 ms
rs=ABjfnFVj2c6_lUpgxbr93j8J5XcedEcimw
41 ms
common.js
36 ms
map.js
50 ms
overlay.js
76 ms
22-blue-dot.png&filter=ff&scale=1.0
115 ms
util.js
87 ms
marker.js
87 ms
poly.js
85 ms
geocoder.js
75 ms
controls.js
102 ms
places_impl.js
75 ms
selection_2x-000.png
28 ms
gen204
70 ms
onion.js
58 ms
openhand_8_8.cur
98 ms
ViewportInfoService.GetViewportInfo
91 ms
stats.js
41 ms
transparent.png
79 ms
undo_poly.png
37 ms
mapcnt6.png
26 ms
tmapctrl4.png
20 ms
vt
54 ms
vt
102 ms
vt
51 ms
vt
56 ms
vt
53 ms
vt
57 ms
vt
96 ms
vt
115 ms
vt
118 ms
vt
110 ms
vt
113 ms
viewer-icons001.png
95 ms
star4.png
100 ms
22-blue-dot.png&scale=1.0
77 ms
gen204
84 ms
AuthenticationService.Authenticate
47 ms
1491-wht-line-blank.png&filter=ff0000FF&scale=1.0
22 ms
MyMaps_Icons003.png
22 ms
mymaps_32.png
24 ms
v1_4593b7d7.png
37 ms
google-my-maps-logo-small-001.png
26 ms
kh
89 ms
rcc.eg 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
rcc.eg 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
rcc.eg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rcc.eg 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 Rcc.eg 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.
rcc.eg
Open Graph description is not detected on the main page of RCC. 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: