Tools & Wizards About Us
fittlesz.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

fittlesz.com

Fittlesz

Page Load Speed

23.6 sec in total

First Response

247 ms

Resources Loaded

22.9 sec

Page Rendered

402 ms

fittlesz.com screenshot

About Website

Click here to check amazing Fittlesz content. Otherwise, check out these important facts you probably never knew about fittlesz.com

Fitt-lesz. Egészségesen, aktívan egy életen át. Természetes szépség. Megoldások a prosztata problémákra. Férfiak egészsége.

Visit fittlesz.com

Key Findings

We analyzed Fittlesz.com page load time and found that the first response time was 247 ms and then it took 23.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fittlesz.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

53/100

10%

Network Requests Diagram

fittlesz.com

247 ms

fittlesz.com

1019 ms

style.css

125 ms

style.css

241 ms

style.min.css

438 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 41% of them (21 requests) were addressed to the original Fittlesz.com, 20% (10 requests) were made to Ajax.googleapis.com and 16% (8 requests) were made to Tfapp.talkfusion.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Cdn.of.talkfusion.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 167.3 kB (39%)

Content Size

434.4 kB

After Optimization

267.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fittlesz.com main page is 434.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 250.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 37.2 kB

  • Original 49.2 kB
  • After minification 47.9 kB
  • After compression 12.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 37.2 kB or 75% of the original size.

Image Optimization

-40%

Potential reduce by 28.5 kB

  • Original 70.9 kB
  • After minification 42.4 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. Obviously, Fittlesz needs image optimization as it can save up to 28.5 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 62.1 kB

  • Original 250.4 kB
  • After minification 246.1 kB
  • After compression 188.3 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 62.1 kB or 25% of the original size.

CSS Optimization

-62%

Potential reduce by 39.6 kB

  • Original 63.9 kB
  • After minification 47.9 kB
  • After compression 24.3 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. Fittlesz.com needs all CSS files to be minified and compressed as it can save up to 39.6 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (70%)

Requests Now

47

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fittlesz.com

fittlesz.com

247 ms

fittlesz.com

fittlesz.com

1019 ms

style.css

style.css

125 ms

style.css

style.css

241 ms

style.min.css

style.min.css

438 ms

style.css

style.css

345 ms

prototype.js

prototype.js

30 ms

scriptaculous.js

scriptaculous.js

34 ms

effects.js

effects.js

38 ms

lightbox-resize.js

lightbox-resize.js

341 ms

jquery.min.js

jquery.min.js

492 ms

jquery-migrate.min.js

jquery-migrate.min.js

342 ms

javascript.js

javascript.js

676 ms

js.js

js.js

454 ms

sharethis.js

sharethis.js

26 ms

element.js

element.js

45 ms

addthis_widget.js

addthis_widget.js

44 ms

wform.asp

wform.asp

174 ms

navigation.js

navigation.js

450 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

451 ms

comment-reply.min.js

comment-reply.min.js

539 ms

akismet-frontend.js

akismet-frontend.js

585 ms

player1.css

player1.css

452 ms

builder.js

builder.js

5 ms

effects.js

effects.js

4 ms

dragdrop.js

dragdrop.js

11 ms

controls.js

controls.js

11 ms

slider.js

slider.js

15 ms

sound.js

sound.js

15 ms

lightbox.css

lightbox.css

119 ms

analytics.js

analytics.js

40 ms

s%C3%BCr%C5%B1erd%C5%91n-a-nap-%C3%A1tsz%C3%BCr%C5%91dik-a-f%C3%A1kon.jpg

s%C3%BCr%C5%B1erd%C5%91n-a-nap-%C3%A1tsz%C3%BCr%C5%91dik-a-f%C3%A1kon.jpg

1324 ms

cropped-Oszi-szines-fej1.jpg

cropped-Oszi-szines-fej1.jpg

273 ms

bels%C5%91-feng-shui.jpg

bels%C5%91-feng-shui.jpg

140 ms

rss.png

rss.png

127 ms

ga.js

ga.js

41 ms

collect

collect

47 ms

_webform.asp

_webform.asp

277 ms

__utm.gif

__utm.gif

11 ms

js

js

64 ms

wform.css

wform.css

304 ms

uniform.elegant.css

uniform.elegant.css

304 ms

style.css

style.css

306 ms

jquery.js

jquery.js

34 ms

jquery.validate.js

jquery.validate.js

314 ms

jcap.js

jcap.js

314 ms

md5.js

md5.js

315 ms

powered.png

powered.png

131 ms

button-bg.jpg

button-bg.jpg

67 ms

t81.png

t81.png

66 ms

32.png

32.png

20182 ms

Accessibility Review

fittlesz.com accessibility score

91

Accessibility Issues

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fittlesz.com best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fittlesz.com SEO score

97

Search Engine Optimization Advices

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

    HU

  • Language Claimed

    HU

  • Encoding

    UTF-8

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

Social Sharing Optimization

fittlesz.com

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