1.9 sec in total
222 ms
1.4 sec
281 ms
Click here to check amazing Sagecity content for South Africa. Otherwise, check out these important facts you probably never knew about sagecity.com
Have a question about your Sage product? Want to learn an advanced feature? Join one or more product support groups in Community Hub, formerly Sage City. Ask your question, collaborate, share experien...
Visit sagecity.comWe analyzed Sagecity.com page load time and found that the first response time was 222 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
sagecity.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value9.9 s
0/100
25%
Value6.7 s
36/100
10%
Value640 ms
47/100
30%
Value0.227
55/100
15%
Value9.6 s
29/100
10%
222 ms
98 ms
22 ms
33 ms
34 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Sagecity.com, 8% (5 requests) were made to Fonts.sage.com and 5% (3 requests) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (275 ms) relates to the external source Communityhub.sage.com.
Page size can be reduced by 260.9 kB (35%)
749.0 kB
488.1 kB
In fact, the total size of Sagecity.com main page is 749.0 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. 50% of websites need less resources to load. Javascripts take 354.4 kB which makes up the majority of the site volume.
Potential reduce by 90.8 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 14.7 kB, which is 14% 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 90.8 kB or 84% of the original size.
Potential reduce by 6.6 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, Sagecity needs image optimization as it can save up to 6.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 82.3 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 82.3 kB or 23% of the original size.
Potential reduce by 81.2 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. Sagecity.com needs all CSS files to be minified and compressed as it can save up to 81.2 kB or 32% of the original size.
Number of requests can be reduced by 35 (69%)
51
16
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sagecity. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
us
222 ms
platform.less
98 ms
jquery.min.js
22 ms
telligent.glow.min.js
33 ms
telligent.evolution.min.js
34 ms
screen.less
275 ms
cssoverrides.less
168 ms
theme.js
34 ms
utag.sync.js
68 ms
7732.js
35 ms
style.less
81 ms
style.less
164 ms
style.less
80 ms
style.less
162 ms
style.less
163 ms
style.less
164 ms
style.less
164 ms
style.less
165 ms
style.less
172 ms
style.less
180 ms
iframeResizer.contentWindow.min.js
33 ms
ui.js
168 ms
ui.js
171 ms
ui.js
174 ms
tablet.less
79 ms
Sage-Community-Hub-logo-247x60.png
29 ms
sage-accounting_4000_3x.png.png_2D00_48x48x2.png
174 ms
sage-50-cloud_4000_3x.png.png_2D00_48x48x2.png
28 ms
default.png_2D00_48x48x2.png
174 ms
sage-timeslips_4000_3x.png.png_2D00_48x48x2.png
29 ms
sage-100-cloud_4000_3x.png.png_2D00_48x48x2.png
174 ms
sage-300-cloud_4000_3x.png.png_2D00_48x48x2.png
83 ms
sage-CRE_4000_3x.png.png_2D00_48x48x2.png
84 ms
sage-fixed-assets_4000_3x.png.png_2D00_48x48x2.png
83 ms
sage-HMRS_4000_3x.png.png_2D00_48x48x2.png
84 ms
sageX3_4000_3x.png.png_2D00_48x48x2.png
84 ms
sage-intacct_4000_3x.png.png_2D00_48x48x2.png
85 ms
sage-people_4000_3x.png.png_2D00_48x48x2.png
86 ms
sage-CRM_4000_3x.png.png_2D00_48x48x2.png
87 ms
GROUP-_2D00_-partner-jade-90x90.png
229 ms
GROUP-icon-_2D00_-Students-_2D00_-jade-90x90.png
87 ms
GROUP-_2D00_-Resources-icon-_2D00_-jade-90x90.png
228 ms
GROUP-_2D00_-Year_2D00_end-_2D00_-jade-90x90.png
87 ms
communityhub.sage.com.json
24 ms
utag.js
80 ms
fe0cd9e3e34eb8a86f099c31f796da84.js
61 ms
Search.png
144 ms
Profileloggedout.png
144 ms
Sage-logo-_2D00_-90x90.png
144 ms
Sage_Text-Regular.woff
226 ms
Sage_Text-Medium.woff
226 ms
Sage_Text-Light.woff
227 ms
Sage_Text-Bold.woff
227 ms
entypo.woff
140 ms
Sage_Headline-Black.woff
225 ms
fontawesome_2D00_webfont.fee66e71.woff
139 ms
feedback_small_32x120.png
128 ms
print.css
130 ms
handheld.less
124 ms
sagecity.com 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
Links do not have a discernible name
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>).
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.
sagecity.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sagecity.com 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
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 Sagecity.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 Sagecity.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.
sagecity.com
Open Graph data is detected on the main page of Sagecity. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: