7.9 sec in total
32 ms
7.2 sec
662 ms
Welcome to citi-wise.com homepage info - get ready to check Citi Wise best content right away, or after learning these important things about citi-wise.com
Visit citi-wise.comWe analyzed Citi-wise.com page load time and found that the first response time was 32 ms and then it took 7.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.
citi-wise.com performance score
name
value
score
weighting
Value14.3 s
0/100
10%
Value45.7 s
0/100
25%
Value14.7 s
1/100
10%
Value680 ms
43/100
30%
Value1.479
0/100
15%
Value42.3 s
0/100
10%
32 ms
544 ms
64 ms
25 ms
216 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 83% of them (122 requests) were addressed to the original Citi-wise.com, 12% (17 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Citi-wise.com.
Page size can be reduced by 870.5 kB (22%)
4.0 MB
3.1 MB
In fact, the total size of Citi-wise.com main page is 4.0 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. Images take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 389.6 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 389.6 kB or 93% of the original size.
Potential reduce by 480.8 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, Citi Wise needs image optimization as it can save up to 480.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 62 B
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. This website has mostly compressed JavaScripts.
We found no issues to fix!
90
90
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citi Wise. According to our analytics all requests are already optimized.
www.citi-wise.com
32 ms
www.citi-wise.com
544 ms
analytics.js
64 ms
wp-emoji-release.min.js
25 ms
front.min.css
216 ms
style.css
205 ms
styles.css
211 ms
svgs-attachment.css
192 ms
css
66 ms
style.css
211 ms
style.css
611 ms
css
79 ms
style.css
796 ms
style.css
385 ms
dashicons.min.css
556 ms
ubermenu.min.css
557 ms
vanilla.css
389 ms
fontawesome-all.min.css
651 ms
extra.css
1195 ms
jquery.js
911 ms
jquery-migrate.min.js
729 ms
frontend.min.js
777 ms
front.min.js
841 ms
cookieControl-8.0.min.js
60 ms
www.citi-wise.com
26 ms
collect
19 ms
www.citi-wise.com
1353 ms
collect
28 ms
mediaelementplayer-legacy.min.css
760 ms
wp-mediaelement.min.css
775 ms
css
16 ms
ubermenu.min.js
912 ms
ubermenu.sticky.min.js
883 ms
jquery.equalizer.js
931 ms
idle-timer.min.js
956 ms
custom.js
1197 ms
masonry.min.js
1200 ms
scripts.min.js
1470 ms
common.js
1194 ms
wp-embed.min.js
1197 ms
mediaelement-and-player.min.js
1602 ms
mediaelement-migrate.min.js
1315 ms
wp-mediaelement.min.js
1367 ms
v
517 ms
no-circle-white-1.svg
333 ms
Aberdeen-225px.png
485 ms
2.png
483 ms
1-150x150.png
486 ms
4-150x150.png
499 ms
5-150x150.png
725 ms
3-150x150.png
727 ms
6-150x150.png
728 ms
Birmingham-225px.png
773 ms
2-150x150.png
729 ms
Bristol-225px.png
916 ms
Chester-225px.png
980 ms
Coventry-225px.png
979 ms
Dublin-225px.png
943 ms
Edinburgh-225px.png
925 ms
Glasgow-225px.png
1081 ms
Harrogate-225px.png
1361 ms
Leeds-225px.png
1344 ms
Liverpool-225px.png
1279 ms
London-225px.png
1397 ms
London-225px-1.png
1401 ms
Manchester-225px.png
1417 ms
Newcastle-225px.png
1615 ms
Nottingham-225px.png
1705 ms
Sheffield-225px.png
1700 ms
Southend-225px.png
1733 ms
Watford-225px.png
1663 ms
Windsor-225px.png
1700 ms
York-225px.png
1958 ms
home-page-image.png
2168 ms
shutterstock_218525794.jpg
1959 ms
ET-Extra.woff
1837 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
66 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
110 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
112 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
112 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdr.ttf
86 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdr.ttf
67 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdr.ttf
85 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7g.ttf
84 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdr.ttf
89 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdr.ttf
86 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_qiTXt_A_A.ttf
131 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_k-UXt_A_A.ttf
133 ms
nuFRD-vYSZviVYUb_rj3ij__anPXDTnCjmHKM4nYO7KN_gGUXt_A_A.ttf
132 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtY.ttf
86 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtY.ttf
88 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDZbtY.ttf
89 ms
ET-Extra.woff
1727 ms
fa-solid-900.woff
1897 ms
fa-regular-400.woff
1758 ms
monarch.ttf
1613 ms
arts-and-culture.png
1810 ms
dinner-1200x720.png
1974 ms
super-street-food.png
1956 ms
mythsandlegends.png
1878 ms
craft-beer.png
1768 ms
Hogmanay-2018-440x264.png
1936 ms
fantastic-facts.png
1919 ms
veggie-1.png
2070 ms
Hogmanay-2018-627x376.png
2220 ms
pagination-loading.gif
1856 ms
no-circle-white-1.svg
251 ms
Aberdeen-225px.png
358 ms
2.png
171 ms
1-150x150.png
185 ms
4-150x150.png
183 ms
5-150x150.png
186 ms
3-150x150.png
343 ms
6-150x150.png
366 ms
Birmingham-225px.png
543 ms
2-150x150.png
357 ms
Bristol-225px.png
698 ms
Chester-225px.png
796 ms
Coventry-225px.png
773 ms
Dublin-225px.png
696 ms
Edinburgh-225px.png
701 ms
Glasgow-225px.png
878 ms
Harrogate-225px.png
1139 ms
Leeds-225px.png
1144 ms
Liverpool-225px.png
1044 ms
London-225px.png
1223 ms
London-225px-1.png
1212 ms
Manchester-225px.png
1210 ms
Newcastle-225px.png
1402 ms
Nottingham-225px.png
1502 ms
Sheffield-225px.png
1484 ms
Southend-225px.png
1547 ms
Watford-225px.png
1545 ms
Windsor-225px.png
1576 ms
York-225px.png
1815 ms
shutterstock_218525794.jpg
1841 ms
arts-and-culture.png
1751 ms
dinner-1200x720.png
1991 ms
super-street-food.png
1906 ms
mythsandlegends.png
1830 ms
craft-beer.png
2111 ms
Hogmanay-2018-440x264.png
2233 ms
fantastic-facts.png
2021 ms
veggie-1.png
2081 ms
Hogmanay-2018-627x376.png
2228 ms
pagination-loading.gif
1981 ms
citi-wise.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.
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
Links do not have a discernible name
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.
citi-wise.com 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
Issues were logged in the Issues panel in Chrome Devtools
citi-wise.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citi-wise.com 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), while the claimed language is English. Our system also found out that Citi-wise.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.
citi-wise.com
Open Graph description is not detected on the main page of Citi Wise. 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: