Tools & Wizards About Us
inbody.fi screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

inbody.fi

InBody | Kehonkoostumus -mittalaitteet ammattikäyttöön

Page Load Speed

3.2 sec in total

First Response

249 ms

Resources Loaded

2.2 sec

Page Rendered

719 ms

inbody.fi screenshot

About Website

Welcome to inbody.fi homepage info - get ready to check In Body best content right away, or after learning these important things about inbody.fi

InBodylla saat monipuolisen kuvan kehon koostumuksesta. Tarkka kehonkoostumusmittaus antaa kuvan kehon hyvinvoinnista ja siihen vaikuttavista elintavoista.

Visit inbody.fi

Key Findings

We analyzed Inbody.fi page load time and found that the first response time was 249 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

inbody.fi performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value3,980 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

inbody.fi

249 ms

inbody.fi

516 ms

prettyPhoto.css

32 ms

wp-video-lightbox.css

30 ms

style.css

36 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 88% of them (99 requests) were addressed to the original Inbody.fi, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (961 ms) belongs to the original domain Inbody.fi.

Page Optimization Overview & Recommendations

Page size can be reduced by 339.5 kB (12%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inbody.fi main page is 2.8 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. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 93.4 kB

  • Original 118.9 kB
  • After minification 117.3 kB
  • After compression 25.5 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 93.4 kB or 79% of the original size.

Image Optimization

-11%

Potential reduce by 231.1 kB

  • Original 2.2 MB
  • After minification 1.9 MB

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, In Body needs image optimization as it can save up to 231.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 7.8 kB

  • Original 302.7 kB
  • After minification 302.7 kB
  • After compression 294.9 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.

CSS Optimization

-4%

Potential reduce by 7.2 kB

  • Original 161.3 kB
  • After minification 159.3 kB
  • After compression 154.2 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. Inbody.fi has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 89 (85%)

Requests Now

105

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In Body. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 34 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

inbody.fi

inbody.fi

249 ms

inbody.fi

inbody.fi

516 ms

prettyPhoto.css

prettyPhoto.css

32 ms

wp-video-lightbox.css

wp-video-lightbox.css

30 ms

style.css

style.css

36 ms

style.min.css

style.min.css

47 ms

blocks.style.build.css

blocks.style.build.css

55 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

40 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

44 ms

views-frontend.css

views-frontend.css

43 ms

cookie-law-info-public.css

cookie-law-info-public.css

41 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

52 ms

embedpress.css

embedpress.css

55 ms

related-products.css

related-products.css

56 ms

swipebox.min.css

swipebox.min.css

58 ms

genericons.css

genericons.css

61 ms

bg-show-hide.css

bg-show-hide.css

60 ms

woocommerce-layout.css

woocommerce-layout.css

63 ms

woocommerce.css

woocommerce.css

65 ms

styles.min.css

styles.min.css

68 ms

learndash_quiz_front.min.css

learndash_quiz_front.min.css

396 ms

jquery.dropdown.min.css

jquery.dropdown.min.css

79 ms

learndash_lesson_video.min.css

learndash_lesson_video.min.css

71 ms

dashicons.min.css

dashicons.min.css

80 ms

learndash.min.css

learndash.min.css

70 ms

toolset_maps_fixes.css

toolset_maps_fixes.css

79 ms

genesis-overrides.css

genesis-overrides.css

84 ms

plyr.css

plyr.css

81 ms

lightslider.css

lightslider.css

85 ms

gts-style.css

gts-style.css

84 ms

font-awesome.min.css

font-awesome.min.css

33 ms

css

css

46 ms

custom.css

custom.css

85 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

87 ms

jquery.min.js

jquery.min.js

437 ms

jquery-migrate.min.js

jquery-migrate.min.js

88 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

87 ms

video-lightbox.js

video-lightbox.js

89 ms

cookie-law-info-public.js

cookie-law-info-public.js

96 ms

plyr.polyfilled.js

plyr.polyfilled.js

78 ms

plugin.js

plugin.js

86 ms

loader

loader

124 ms

wc-blocks.css

wc-blocks.css

73 ms

cookie-law-info-table.css

cookie-law-info-table.css

78 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

76 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

77 ms

js.cookie-2.2.1.min.js

js.cookie-2.2.1.min.js

82 ms

woocommerce.min.js

woocommerce.min.js

83 ms

lightslider.min.js

lightslider.min.js

79 ms

responsive-menu.js

responsive-menu.js

74 ms

custom.js

custom.js

82 ms

email-decode.min.js

email-decode.min.js

71 ms

pdfobject.min.js

pdfobject.min.js

83 ms

initplyr.js

initplyr.js

83 ms

vimeo-player.js

vimeo-player.js

78 ms

front.js

front.js

78 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

85 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

80 ms

wp-polyfill.min.js

wp-polyfill.min.js

82 ms

react.min.js

react.min.js

73 ms

hooks.min.js

hooks.min.js

80 ms

deprecated.min.js

deprecated.min.js

82 ms

dom.min.js

dom.min.js

78 ms

react-dom.min.js

react-dom.min.js

80 ms

escape-html.min.js

escape-html.min.js

85 ms

element.min.js

element.min.js

84 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

475 ms

i18n.min.js

i18n.min.js

87 ms

keycodes.min.js

keycodes.min.js

90 ms

priority-queue.min.js

priority-queue.min.js

90 ms

compose.min.js

compose.min.js

99 ms

private-apis.min.js

private-apis.min.js

97 ms

redux-routine.min.js

redux-routine.min.js

97 ms

data.min.js

data.min.js

98 ms

ads.js

ads.js

96 ms

documents-viewer-script.js

documents-viewer-script.js

458 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

96 ms

underscore.min.js

underscore.min.js

95 ms

front.js

front.js

104 ms

effect.min.js

effect.min.js

104 ms

effect-slide.min.js

effect-slide.min.js

105 ms

effect-highlight.min.js

effect-highlight.min.js

105 ms

effect-fold.min.js

effect-fold.min.js

115 ms

effect-blind.min.js

effect-blind.min.js

119 ms

bg-show-hide.js

bg-show-hide.js

132 ms

sourcebuster.min.js

sourcebuster.min.js

124 ms

order-attribution.min.js

order-attribution.min.js

130 ms

learndash.js

learndash.js

131 ms

loader.min.js

loader.min.js

66 ms

lftracker_v1_p1e024ByqoJ7GB6d.js

lftracker_v1_p1e024ByqoJ7GB6d.js

559 ms

gtm.js

gtm.js

214 ms

logo-inbody.png

logo-inbody.png

86 ms

Group-3-4.png

Group-3-4.png

961 ms

image-17.png

image-17.png

88 ms

image-12.png

image-12.png

107 ms

image-18.png

image-18.png

109 ms

image-19.png

image-19.png

108 ms

image-20.png

image-20.png

95 ms

image-21.png

image-21.png

108 ms

inbody_referenssit.jpg

inbody_referenssit.jpg

872 ms

Group-12-4.png

Group-12-4.png

791 ms

Group-5-3.png

Group-5-3.png

190 ms

image-23-2.png

image-23-2.png

110 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

39 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

39 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

118 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

121 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

36 ms

diffuser.js

diffuser.js

119 ms

controls.png

controls.png

12 ms

prism.app-us1.com

prism.app-us1.com

115 ms

tr-rc.lfeeder.com

tr-rc.lfeeder.com

44 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

13 ms

Accessibility Review

inbody.fi accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

inbody.fi best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

inbody.fi SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inbody.fi can be misinterpreted by Google and other search engines. Our service has detected that Finnish is used on the page, and it matches the claimed language. Our system also found out that Inbody.fi 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.

Social Sharing Optimization

inbody.fi

Open Graph data is detected on the main page of In Body. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: