4.5 sec in total
489 ms
3 sec
1 sec
Visit gym64.com now to see the best up-to-date Gym 64 content and also check out these interesting facts you probably never knew about gym64.com
No 1 Gym in Fife! Gym 64 is a family-run business and passionate about our members with branches in Dunfermline, Kirkcaldy & Glenrothes.
Visit gym64.comWe analyzed Gym64.com page load time and found that the first response time was 489 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gym64.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value77.9 s
0/100
25%
Value7.2 s
29/100
10%
Value180 ms
91/100
30%
Value0.041
99/100
15%
Value11.4 s
19/100
10%
489 ms
324 ms
461 ms
253 ms
462 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 99% of them (109 requests) were addressed to the original Gym64.com, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (827 ms) belongs to the original domain Gym64.com.
Page size can be reduced by 472.9 kB (18%)
2.7 MB
2.2 MB
In fact, the total size of Gym64.com main page is 2.7 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 304.9 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 304.9 kB or 88% of the original size.
Potential reduce by 1.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. Gym 64 images are well optimized though.
Potential reduce by 22.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 144.0 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. Gym64.com needs all CSS files to be minified and compressed as it can save up to 144.0 kB or 61% of the original size.
Number of requests can be reduced by 81 (76%)
107
26
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gym 64. 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 20 to 1 for CSS and as a result speed up the page load time.
gym64.com
489 ms
autoptimize_4ddcd1fe179d3017537fee6f8a41a0b2.css
324 ms
jquery.min.js
461 ms
jquery-migrate.min.js
253 ms
autoptimize_single_4a23d8fc913027f01095e881697e0a26.js
462 ms
headerScript.min.js
256 ms
jquery.blockUI.min.js
257 ms
add-to-cart.min.js
461 ms
js.cookie.min.js
461 ms
woocommerce.min.js
462 ms
autoptimize_single_33fa353be8c10eb1d23662462b650434.js
484 ms
underscore.min.js
483 ms
wp-util.min.js
483 ms
add-to-cart-variation.min.js
484 ms
general.min.js
418 ms
pdfobject.min.js
480 ms
autoptimize_single_f2f80908b3ea875ec6b33015deb3f3ec.js
480 ms
autoptimize_single_bcc8add94240ffcbc77df45ea613492f.js
481 ms
autoptimize_single_a482c36d7a7284c7bdf6734a7b8ee8dd.js
483 ms
wp-polyfill-inert.min.js
481 ms
regenerator-runtime.min.js
480 ms
wp-polyfill.min.js
562 ms
react.min.js
576 ms
hooks.min.js
577 ms
deprecated.min.js
577 ms
dom.min.js
577 ms
react-dom.min.js
687 ms
escape-html.min.js
640 ms
element.min.js
641 ms
is-shallow-equal.min.js
672 ms
i18n.min.js
641 ms
keycodes.min.js
687 ms
priority-queue.min.js
718 ms
compose.min.js
719 ms
private-apis.min.js
720 ms
redux-routine.min.js
720 ms
data.min.js
541 ms
autoptimize_single_3a3811c66815d894f8449d8bf86b823b.js
542 ms
autoptimize_single_8410e7f028ab2f9428a255d628a7e5f6.js
611 ms
gtm.js
145 ms
owl.carousel.min.js
409 ms
frontend.min.js
408 ms
modals.min.js
415 ms
complianz.min.js
416 ms
jquery.smartmenus.min.js
483 ms
autoptimize_single_ad42b6ce23db453400c6a87058469d0e.css
465 ms
autoptimize_single_88495cbabc81a6cb00f350444f9384ce.css
489 ms
autoptimize_single_d8bbd4c63fff9124dbca70e1bcec7cda.css
496 ms
autoptimize_single_84ca987b69f968384cdf7755d24cb078.css
503 ms
autoptimize_single_52b4aa2d5b5465c3f56a4087da2ec1a3.css
511 ms
autoptimize_single_ad6b126dda15299378ff45200fa6b15b.css
597 ms
autoptimize_single_812482f16c4e39960f238f39f2e7f0fb.css
550 ms
autoptimize_single_279a41fe094a1c0ff59f6d84dc6ec0d2.css
542 ms
autoptimize_single_54f92eb94e19c0715a08d9d2a298ecc5.css
556 ms
elementor-icons.min.css
564 ms
autoptimize_single_7cb931c72f57de260e5f48ec1ebd6d2e.css
570 ms
autoptimize_single_9bf1547406580f9a2cfa8968606b0d38.css
696 ms
dashicons.min.css
613 ms
autoptimize_single_4c9bfb52edcef27891679316b5a3e474.css
603 ms
autoptimize_single_6d64f8f7793f7154d8fe76b2884daaed.css
606 ms
autoptimize_single_8b516fbfaf169bb09bd1bf9a594a904f.css
607 ms
autoptimize_single_5a976514054480cf53d495f08d393456.css
608 ms
solid.min.css
547 ms
cart-fragments.min.js
555 ms
webpack.runtime.min.js
524 ms
frontend-modules.min.js
512 ms
waypoints.min.js
504 ms
core.min.js
653 ms
frontend.min.js
635 ms
autoptimize_single_72930945275d026f1c88ebd9ac8a8062.js
634 ms
webpack-pro.runtime.min.js
633 ms
frontend.min.js
634 ms
elements-handlers.min.js
634 ms
jquery.sticky.min.js
629 ms
mptt-functions.min.js
560 ms
event.min.js
561 ms
mptt-elementor-editor.min.js
561 ms
jquery.zoom.min.js
558 ms
jquery.flexslider.min.js
555 ms
photoswipe.min.js
562 ms
photoswipe-ui-default.min.js
489 ms
single-product.min.js
471 ms
lazyload.min.js
459 ms
eicons.woff
601 ms
fa-solid-900.woff
616 ms
video-background.jpg
645 ms
shape-17.png
404 ms
Action-photo_04-scaled.jpg
712 ms
Action-photo_14-scaled.jpg
704 ms
Action-photo_37-scaled-1.jpg
774 ms
footer.jpg
556 ms
gym64.com
827 ms
G64-Logo-qez13ab6m43nibj6b4gucorpfw8zxeh872c798b0ec.png
306 ms
angle-lines-cropped-yellow.svg
364 ms
G64-CNP-Logo.png
386 ms
G64-Nespresso-Logo.png
442 ms
G64-GSN-Logo.png
442 ms
G64-Superlean-LogoV2.png
443 ms
001-parking-area.png
465 ms
003-towel.png
521 ms
sun.png
520 ms
wifi-signal.png
521 ms
006-calendar.png
522 ms
007-yoga.png
543 ms
008-drink.png
598 ms
shower.png
599 ms
010-body-scan.png
599 ms
G64-Logo-qez13ab6dccha1daak13mw61b73ig88bjeiqfjik1o.png
599 ms
81AB9B49-A502-47C2-A38A-83751D1CA16C-1024x347.png
623 ms
autoptimize_single_29ed0396622780590223cd919f310dd7.css
80 ms
gym64.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.
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
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
gym64.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
gym64.com SEO score
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 Gym64.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 Gym64.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.
gym64.com
Open Graph data is detected on the main page of Gym 64. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: