19.8 sec in total
6.6 sec
12.7 sec
433 ms
Click here to check amazing Fleely content for India. Otherwise, check out these important facts you probably never knew about fleely.com
Fleely Provides Electric Vehicle Charging Stations, Electric Vehicle Station , EV Charging Station Installation Service to all over the India
Visit fleely.comWe analyzed Fleely.com page load time and found that the first response time was 6.6 sec and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fleely.com performance score
name
value
score
weighting
Value11.3 s
0/100
10%
Value12.2 s
0/100
25%
Value36.0 s
0/100
10%
Value28,210 ms
0/100
30%
Value0.089
92/100
15%
Value43.9 s
0/100
10%
6603 ms
438 ms
442 ms
440 ms
685 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 84% of them (100 requests) were addressed to the original Fleely.com, 10% (12 requests) were made to Embed.tawk.to and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Fleely.com.
Page size can be reduced by 458.2 kB (45%)
1.0 MB
566.7 kB
In fact, the total size of Fleely.com main page is 1.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. 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. HTML takes 444.6 kB which makes up the majority of the site volume.
Potential reduce by 396.1 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 396.1 kB or 89% of the original size.
Potential reduce by 4.5 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. Fleely images are well optimized though.
Potential reduce by 14.2 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. This website has mostly compressed JavaScripts.
Potential reduce by 43.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. Fleely.com needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 19% of the original size.
Number of requests can be reduced by 89 (91%)
98
9
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fleely. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
fleely.com
6603 ms
wp-emoji-release.min.js
438 ms
style.min.css
442 ms
wc-blocks-vendors-style.css
440 ms
wc-blocks-style.css
685 ms
all-css.min.css
698 ms
asl_responsive.css
636 ms
magnific-popup.css
655 ms
be-gdpr-public.css
659 ms
styles.css
657 ms
tatsu.min.css
872 ms
exponent-modules.min.css
880 ms
rs6.css
883 ms
typehub-public.css
882 ms
bootstrap.css
910 ms
arf_front.css
927 ms
flag_icon.css
1094 ms
maincss_materialize_103.css
1313 ms
materialize.css
1098 ms
css
15 ms
tatsu-icons.css
1102 ms
vendor.min.css
1133 ms
main.min.css
1169 ms
woocommerce.min.css
1323 ms
icons.css
1319 ms
style.css
1319 ms
jquery.min.js
1367 ms
jquery-migrate.min.js
1399 ms
be-gdpr-public.js
1530 ms
revolution.tools.min.js
1770 ms
rs6.min.js
1999 ms
webfont.min.js
1546 ms
materialize.js
1592 ms
modernizr.min.js
1628 ms
maincss_materialize_103.css
1567 ms
materialize.css
1582 ms
materialize.js
1632 ms
js
54 ms
bootstrap-select.css
1455 ms
comment-reply.min.js
1541 ms
magnificpopup.min.js
1559 ms
regenerator-runtime.min.js
1550 ms
wp-polyfill.min.js
2799 ms
index.js
2783 ms
helpers.min.js
2781 ms
debouncedresize.min.js
2780 ms
asyncloader.min.js
2743 ms
exp-modules.min.js
2729 ms
es6-promise.auto.min.js
2562 ms
core.min.js
2560 ms
accordion.min.js
2560 ms
tabs.min.js
2557 ms
tatsu.min.js
2532 ms
tatsu-header.min.js
2512 ms
jquery.blockUI.min.js
2349 ms
add-to-cart.min.js
2345 ms
js.cookie.min.js
2363 ms
woocommerce.min.js
2332 ms
cart-fragments.min.js
2293 ms
css
28 ms
underscore.min.js
2150 ms
wp-util.min.js
2146 ms
add-to-cart-variation.min.js
2146 ms
woocommerce.min.js
2744 ms
main.min.js
2692 ms
bootstrap.min.js
2666 ms
jqBootstrapValidation.js
2539 ms
bootstrap-select.js
2524 ms
arforms.js
2485 ms
arf_conditional_logic.js
2447 ms
arf_modal_js.js
2324 ms
mobile-app-intro-bg.svg
1520 ms
0a366df26015da2d45f9ae0cfb71c462
253 ms
Fleey.png
969 ms
tesla-model-3-charging.jpeg
968 ms
ev-charging-2.png
968 ms
download-1.png
968 ms
download.png
968 ms
MG.jpg
968 ms
mahindra-ev.png
968 ms
tesla-ev.png
859 ms
kia-ev.jpeg
858 ms
BMW.jpg
858 ms
ashok-leyland-ev.png
856 ms
fleely-60kW-CCS2-Dual-Gun-2-768x432.png
935 ms
submit_btn_image.gif
643 ms
app-google-play.png
854 ms
apple-app-store.png
853 ms
tatsu-icons.ttf
1399 ms
exponent.ttf
834 ms
select_arrow.svg
804 ms
default
717 ms
analytics.js
704 ms
Fleey.png
1131 ms
flickity.min.js
824 ms
isotope.min.js
822 ms
begrid.min.js
822 ms
tilt.min.js
812 ms
countTo.min.js
805 ms
superfish.min.js
800 ms
hoverintent.min.js
800 ms
tesla-model-3-charging.jpeg
905 ms
fleely-ev-station.png
905 ms
ev-fleely-automaker.png
905 ms
ev-fleely-charging.png
905 ms
modulobox.min.js
735 ms
collect
130 ms
modulobox.svg
223 ms
twk-arr-find-polyfill.js
197 ms
twk-object-values-polyfill.js
183 ms
twk-event-polyfill.js
57 ms
twk-entries-polyfill.js
65 ms
twk-iterator-polyfill.js
220 ms
twk-main.js
71 ms
twk-vendor.js
182 ms
twk-chunk-vendors.js
249 ms
twk-chunk-common.js
270 ms
twk-runtime.js
230 ms
twk-app.js
228 ms
fleely.com 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
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
fleely.com 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
fleely.com 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
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 Fleely.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 Fleely.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.
fleely.com
Open Graph data is detected on the main page of Fleely. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: