Tools & Wizards About Us
worldynamics.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 47

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

worldynamics.com

WORLDYNAMICS

Page Load Speed

2.2 sec in total

First Response

129 ms

Resources Loaded

1.7 sec

Page Rendered

376 ms

worldynamics.com screenshot

About Website

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

WORLDYNAMICS

Visit worldynamics.com

Key Findings

We analyzed Worldynamics.com page load time and found that the first response time was 129 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

worldynamics.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

worldynamics.com

129 ms

worldynamics.com

227 ms

worldynamics.org

154 ms

worldynamics.org

289 ms

bootstrap.css

58 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Worldynamics.com, 78% (45 requests) were made to Worldynamics.org and 10% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (424 ms) relates to the external source Worldynamics.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.9 kB (7%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldynamics.com main page is 2.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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 33.9 kB

  • Original 41.3 kB
  • After minification 37.4 kB
  • After compression 7.4 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 33.9 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 96.5 kB

  • Original 1.8 MB
  • After minification 1.7 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. WORLDYNAMICS images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 8.9 kB

  • Original 175.9 kB
  • After minification 175.9 kB
  • After compression 167.0 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

-9%

Potential reduce by 2.6 kB

  • Original 29.4 kB
  • After minification 29.4 kB
  • After compression 26.9 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. Worldynamics.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (53%)

Requests Now

47

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldynamics.com

worldynamics.com

129 ms

worldynamics.com

worldynamics.com

227 ms

worldynamics.org

worldynamics.org

154 ms

worldynamics.org

worldynamics.org

289 ms

bootstrap.css

bootstrap.css

58 ms

style.css

style.css

112 ms

jquery.fancybox.css

jquery.fancybox.css

162 ms

contact-form.css

contact-form.css

163 ms

jquery.js

jquery.js

220 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

164 ms

jquery.fancybox.js

jquery.fancybox.js

232 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

170 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

214 ms

TMForm.js

TMForm.js

269 ms

jquery.vide.min.js

jquery.vide.min.js

216 ms

js

js

47 ms

jquery.equalheights.min.js

jquery.equalheights.min.js

235 ms

bootstrap.min.js

bootstrap.min.js

333 ms

tm-scripts.js

tm-scripts.js

331 ms

font-awesome.min.css

font-awesome.min.css

30 ms

css

css

35 ms

css

css

53 ms

bg-img-2.jpg

bg-img-2.jpg

215 ms

bg-img-3.jpg

bg-img-3.jpg

268 ms

bg-img-4.jpg

bg-img-4.jpg

264 ms

bg-img-5.jpg

bg-img-5.jpg

214 ms

logo.gif

logo.gif

327 ms

bg-img-1.jpg

bg-img-1.jpg

115 ms

page1-img32.jpg

page1-img32.jpg

215 ms

page1-img1.jpg

page1-img1.jpg

319 ms

page1-img2.jpg

page1-img2.jpg

268 ms

1a.png

1a.png

269 ms

flecha.png

flecha.png

317 ms

1b.png

1b.png

324 ms

1c.png

1c.png

324 ms

1d.png

1d.png

324 ms

loghi.jpg

loghi.jpg

368 ms

1.jpg

1.jpg

424 ms

2.jpg

2.jpg

378 ms

3.jpg

3.jpg

378 ms

securimage_show.php

securimage_show.php

404 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

34 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

34 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

44 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

53 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

54 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

23 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

54 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

314 ms

device.min.js

device.min.js

354 ms

superfish.js

superfish.js

365 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

365 ms

tmstickup.js

tmstickup.js

366 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

392 ms

jquery.simplr.smoothscroll.min.js

jquery.simplr.smoothscroll.min.js

405 ms

jquery.rd-parallax.js

jquery.rd-parallax.js

408 ms

jquery.ui.totop.js

jquery.ui.totop.js

418 ms

video.jpg

video.jpg

108 ms

Accessibility Review

worldynamics.com accessibility score

47

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

worldynamics.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

worldynamics.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Worldynamics.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 Worldynamics.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

worldynamics.com

Open Graph description is not detected on the main page of WORLDYNAMICS. 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: