3.2 sec in total
539 ms
2.1 sec
518 ms
Click here to check amazing Nani Co content. Otherwise, check out these important facts you probably never knew about nani.co.ke
Visit nani.co.keWe analyzed Nani.co.ke page load time and found that the first response time was 539 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
nani.co.ke performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value13.7 s
0/100
25%
Value7.5 s
26/100
10%
Value250 ms
85/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
539 ms
357 ms
294 ms
297 ms
312 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 79% of them (61 requests) were addressed to the original Nani.co.ke, 5% (4 requests) were made to I0.wp.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (936 ms) belongs to the original domain Nani.co.ke.
Page size can be reduced by 182.8 kB (5%)
3.5 MB
3.3 MB
In fact, the total size of Nani.co.ke main page is 3.5 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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 86.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. 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 86.8 kB or 78% of the original size.
Potential reduce by 32.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. Nani Co images are well optimized though.
Potential reduce by 48.5 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 48.5 kB or 13% of the original size.
Potential reduce by 14.8 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. Nani.co.ke has all CSS files already compressed.
Number of requests can be reduced by 55 (80%)
69
14
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nani Co. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
nani.co.ke
539 ms
style.min.css
357 ms
mediaelementplayer-legacy.min.css
294 ms
wp-mediaelement.min.css
297 ms
styles.css
312 ms
cf7msm.css
311 ms
menu-image.css
326 ms
dashicons.min.css
455 ms
swiper.min.css
384 ms
font-awesome.min.css
399 ms
deprecated-style.min.css
408 ms
style.min.css
411 ms
style.css
528 ms
grid.min.css
465 ms
js_composer.min.css
637 ms
smartslider.min.css
499 ms
css
37 ms
n2.min.js
500 ms
smartslider-frontend.min.js
551 ms
ss-simple.min.js
551 ms
w-arrow-image.min.js
585 ms
w-bullet.min.js
589 ms
jquery.min.js
616 ms
jquery-migrate.min.js
632 ms
jquery.bind-first-0.2.3.min.js
631 ms
js.cookie-2.1.3.min.js
672 ms
public.js
686 ms
animate.min.css
740 ms
css
25 ms
aos.css
744 ms
ionicons.min.css
744 ms
style.css
752 ms
hooks.min.js
753 ms
i18n.min.js
753 ms
index.js
752 ms
index.js
927 ms
cf7msm.min.js
934 ms
woocommerce-hack.js
934 ms
e-202447.js
34 ms
js_composer_front.min.js
936 ms
vc-waypoints.min.js
728 ms
sp-scripts.min.js
725 ms
swiper.min.js
861 ms
imagesloaded.min.js
775 ms
masonry.min.js
790 ms
jquery.masonry.min.js
759 ms
underscore.min.js
731 ms
aos.js
685 ms
isotope.pkgd.min.js
769 ms
jquery.mega-menu.min.js
753 ms
navigation.js
729 ms
skip-link-focus-fix.js
702 ms
owl.carousel.min.js
684 ms
main.js
759 ms
dark.png
303 ms
logo-e1599547888587.png
675 ms
Group-54-1-1-scaled.jpg
356 ms
Group-55.jpg
472 ms
Group-54-1.jpg
434 ms
Group-49.png
531 ms
Rectangle-172.png
713 ms
Group-50.png
925 ms
Rectangle-176.png
355 ms
Rectangle-175.png
358 ms
Rectangle-173.png
357 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf
229 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf
259 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
280 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
282 ms
Raleway-Bold.ttf
597 ms
fontawesome-webfont.woff
636 ms
embed
378 ms
ionicons.ttf
505 ms
js
32 ms
search.js
4 ms
geometry.js
6 ms
main.js
11 ms
nani.co.ke accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
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
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.
nani.co.ke 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
Browser errors were logged to the console
Page has valid source maps
nani.co.ke SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 Nani.co.ke 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 Nani.co.ke 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.
nani.co.ke
Open Graph description is not detected on the main page of Nani Co. 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: