6.8 sec in total
944 ms
5.1 sec
760 ms
Click here to check amazing Fenetic Wellbeing content. Otherwise, check out these important facts you probably never knew about feneticwellbeing.co.uk
At Fenetic Wellbeing we sell a range of wheelchairs, recliner chairs, mobility scooters, and other mobility aids to support independent living.
Visit feneticwellbeing.co.ukWe analyzed Feneticwellbeing.co.uk page load time and found that the first response time was 944 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
feneticwellbeing.co.uk performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value4.8 s
31/100
25%
Value31.4 s
0/100
10%
Value99,630 ms
0/100
30%
Value0.127
82/100
15%
Value131.9 s
0/100
10%
944 ms
80 ms
163 ms
239 ms
418 ms
Our browser made a total of 215 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Feneticwellbeing.co.uk, 3% (7 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Feneticwellbeing.com.
Page size can be reduced by 707.2 kB (18%)
3.9 MB
3.2 MB
In fact, the total size of Feneticwellbeing.co.uk main page is 3.9 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. 85% 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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 111.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 111.1 kB or 87% of the original size.
Potential reduce by 2.0 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. Fenetic Wellbeing images are well optimized though.
Potential reduce by 278.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 278.5 kB or 41% of the original size.
Potential reduce by 315.6 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. Feneticwellbeing.co.uk needs all CSS files to be minified and compressed as it can save up to 315.6 kB or 73% of the original size.
Number of requests can be reduced by 166 (81%)
205
39
The browser has sent 205 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fenetic Wellbeing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 158 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
www.feneticwellbeing.com
944 ms
calendar.css
80 ms
normalize.css
163 ms
fonts.css
239 ms
styles.css
418 ms
icons.css
243 ms
fontawesome-all.min.css
247 ms
searchsuiteautocomplete.css
243 ms
stripe_payments.css
250 ms
require.js
397 ms
mixins.js
321 ms
requirejs-config.js
321 ms
polyfill.js
336 ms
stripe_payments.js
337 ms
css
45 ms
the-fenetic-trading-company
185 ms
gtm.js
153 ms
logo.png
152 ms
cullingworth-which-logo-simple-2021.png
151 ms
large-fenetic-hero-dec20.jpg
150 ms
landing_underline.png
151 ms
dario-valenzuela-PAGBeJrLiDA-unsplash.jpg
1391 ms
jquery.mobile.custom.js
148 ms
dataPost.js
249 ms
bootstrap.js
249 ms
jquery.js
322 ms
translate-inline.js
246 ms
fenetic_app.js
242 ms
fenetic.lazysizes.js
316 ms
contrast.svg
299 ms
feefo-svg.svg
296 ms
feefo-stars-outline.png
299 ms
feefo-stars-fill.png
446 ms
translate.js
444 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
41 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
106 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
158 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
157 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
158 ms
header-search.svg
420 ms
header-phone.svg
422 ms
basket.svg
418 ms
jquery.cookie.js
569 ms
5vwuQrxPOv8
220 ms
free-delivery.svg
549 ms
secure-payments.svg
549 ms
feefo-platinum-wide-dark.svg
629 ms
wheelchair-3948122_960_720.jpg
1210 ms
FW_LIGHTWEIGHT_WHEELCHAIR-1024x683.jpg
1208 ms
cookies.js
586 ms
fenetic-icons.woff
583 ms
fenetic-logo-white.png
962 ms
feefo-platinum-wide-white.svg
963 ms
jquery.js
932 ms
conversion_async.js
230 ms
optimize.js
277 ms
bat.js
296 ms
6ba7a0e1-cfd7-456f-89fc-66f59ed3b8a2.js
456 ms
fbevents.js
225 ms
hotjar-2535378.js
372 ms
js
119 ms
feefo-widget.js
230 ms
template.js
1107 ms
confirm.js
1108 ms
widget.js
1106 ms
main.js
1105 ms
bootstrap.js
1105 ms
dialog.js
1312 ms
www-player.css
260 ms
www-embed-player.js
299 ms
base.js
480 ms
fetch-polyfill.js
186 ms
compat.js
1307 ms
common.js
1247 ms
jquery-migrate.js
1245 ms
slick.js
1245 ms
jquery.matchheight.js
1245 ms
ls.bgset.min.js
1268 ms
ls.unveilhooks.min.js
1269 ms
lazysizes.min.js
1267 ms
220 ms
mage.js
1147 ms
511312872348982
118 ms
analytics.js
128 ms
asset_composer.js
412 ms
5188140.js
535 ms
modules.cbd9768ba80ba0be5b17.js
317 ms
collect
29 ms
collect
66 ms
568 ms
main1.min.js
391 ms
3.3.0.js
563 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
634 ms
ga-audiences
620 ms
ad_status.js
365 ms
VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js
190 ms
embed.js
119 ms
id
113 ms
3uNJDga6zfo0UMIzr1xZlUgRZThYVyuW
292 ms
jquery.storageapi.min.js
284 ms
5188140
306 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
198 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
197 ms
underscore.js
239 ms
knockout.js
455 ms
knockout-es5.js
383 ms
domReady.js
380 ms
modal.js
382 ms
visit-data
767 ms
engine.js
323 ms
bootstrap.js
322 ms
observable_array.js
397 ms
bound-nodes.js
396 ms
scripts.js
395 ms
core.js
248 ms
accordion.js
251 ms
autocomplete.js
337 ms
button.js
338 ms
datepicker.js
336 ms
draggable.js
337 ms
droppable.js
336 ms
effect-blind.js
338 ms
effect-bounce.js
476 ms
effect-clip.js
474 ms
effect-drop.js
474 ms
effect-explode.js
472 ms
effect-fade.js
474 ms
effect-fold.js
467 ms
effect-highlight.js
475 ms
effect-scale.js
477 ms
effect-pulsate.js
493 ms
effect-shake.js
477 ms
effect-slide.js
493 ms
effect-transfer.js
474 ms
effect.js
608 ms
menu.js
592 ms
mouse.js
589 ms
position.js
590 ms
progressbar.js
591 ms
resizable.js
591 ms
Create
39 ms
selectable.js
677 ms
clarity.js
106 ms
slider.js
532 ms
sortable.js
533 ms
spinner.js
528 ms
tabs.js
530 ms
timepicker.js
539 ms
widget_v2.334.js
97 ms
tooltip.js
514 ms
knockout-repeat.js
514 ms
knockout-fast-foreach.js
515 ms
text.js
515 ms
key-codes.js
513 ms
renderer.js
563 ms
resizable.js
488 ms
i18n.js
488 ms
scope.js
488 ms
range.js
488 ms
mage-init.js
488 ms
keyboard.js
529 ms
optgroup.js
400 ms
after-render.js
410 ms
autoselect.js
410 ms
datepicker.js
411 ms
outer_click.js
411 ms
fadeVisible.js
477 ms
collapsible.js
478 ms
staticChecked.js
494 ms
simple-checked.js
494 ms
bind-html.js
480 ms
tooltip.js
479 ms
color-picker.js
427 ms
observable_source.js
425 ms
console-logger.js
430 ms
wrapper.js
429 ms
events.js
435 ms
es6-collections.js
435 ms
zealcarttotalonly
536 ms
modal-popup.html
296 ms
modal-slide.html
307 ms
modal-custom.html
319 ms
js-translation.json
308 ms
async.js
315 ms
registry.js
359 ms
loader.js
350 ms
main.js
336 ms
calendar.js
328 ms
moment.js
324 ms
GenerateIT
35 ms
tooltip.html
299 ms
spectrum.js
248 ms
tinycolor.js
247 ms
class.js
255 ms
local.js
253 ms
logger.js
309 ms
entry-factory.js
313 ms
console-output-handler.js
313 ms
formatter.js
327 ms
message-pool.js
327 ms
levels-pool.js
371 ms
logger-utils.js
383 ms
dom-observer.js
284 ms
bindings.js
284 ms
arrays.js
462 ms
compare.js
462 ms
misc.js
462 ms
objects.js
462 ms
strings.js
462 ms
template.js
463 ms
entry.js
317 ms
avatar_simple_visitor.png
103 ms
MutationObserver.js
81 ms
hbABjQBLsAhQWLEBAY5ZsUYGK1ghsBBZS7AUUlghsIBZHbAGK1xYWbAUKwAAAAFcPYvrAAA=
8 ms
FormData.js
81 ms
feneticwellbeing.co.uk accessibility score
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
feneticwellbeing.co.uk 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
Page has valid source maps
feneticwellbeing.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Feneticwellbeing.co.uk 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 Feneticwellbeing.co.uk 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.
feneticwellbeing.co.uk
Open Graph description is not detected on the main page of Fenetic Wellbeing. 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: