Access wttfuture.wordpress.com. Welcome to the future | Everything you need to know about mobile augmented reality experiences for b...

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value4,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.143

78/100

15%

TTI (Time to Interactive)

Value29.3 s

0/100

10%

wttfuture.wordpress.com

11 ms

wttfuture.wordpress.com

681 ms

83 ms

94 ms

100 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Wttfuture.wordpress.com, 16% (19 requests) were made to 0.gravatar.com and 14% (16 requests) were made to 2.gravatar.com. The less responsive or slowest element that took the longest time to load (10.3 sec) relates to the external source I1.wp.com.

Content Size

2.4 MB

After Optimization

1.6 MB

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

HTML Optimization

-77%

Potential reduce by 91.8 kB

Original 119.5 kB
After minification 118.6 kB
After compression 27.7 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 91.8 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 27.8 kB

Original 1.3 MB
After minification 1.3 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. Wtt Future Wordpress images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 473.8 kB

Original 683.4 kB
After minification 572.8 kB
After compression 209.6 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 473.8 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 234.7 kB

Original 288.2 kB
After minification 285.7 kB
After compression 53.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. Wttfuture.wordpress.com needs all CSS files to be minified and compressed as it can save up to 234.7 kB or 81% of the original size.

Requests Now

106

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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.

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Wttfuture.wordpress.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 Wttfuture.wordpress.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

wttfuture.wordpress.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Welcome to the future | Everything you need to know about mobile augmented reality experiences for brand communication and more.

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

wttfuture.wordpress.com

wttfuture.wordpress.com

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

wttfuture.wordpress.com

wttfuture.wordpress.com

style.css

gprofiles.js

wpgroho.js

rating.js

jetpack-carousel.css

tiled-gallery.css

widgets.js

725X1342.skimlinks.js

w.js

merriweather.css

header-wttfuture-v22.png

h1.gif

4ab13b88acba61b4bf0b87b273df33e4

microsoft-hololens-skype-rgb.png

mary-jo-foley-60x45.jpg

9c6W4CCU9M4

92rYjlxqypM

sidebar.gif

2f245bba07dcfcd25998e987dc0f8bba

24uur.png

img-effie-awards.jpeg

238943-mobile-world-congress.jpg

red-small.png

58a-tabworld-def-22092014.jpg

hololens-review-970-80.jpg

ingress-game.png

h2.gif

roadtofortaleza-600x324.png

5f6d8c177b829cac9a3a47d8dc27361e

29503336d210d4e241c4c02933bf8e07

2b7167cf87e38b64c3a2119ff98903c6

8a1557424006d98da892300d938c6900

53d5f8d4b3d3944afc5afb2d4e02e4d9

25424eaca61adbef158360d4339707f3

8c4d75b3fea946cf5517d6fbfecb5c5a

e0f7c0d7c65c59199ece65df47996e64

5d6f3e3fd9767624bcc36c1a8d56d333

eb84a977b93362e75ec066af028f1502

bdcb64f72730334657fe46b3374f6af8

5434216985d593e6cb0afbf985314557

2b62ed733a967299649b29085c5054cf

8bc8ab9a1c3886e5875c45217dcb0b99

51ba0f68ba627b513185ed9205507eaa

0d8d0b5cc5817b2ee674aba78c062eaa