Tools & Wizards About Us
thomasmathew.net screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

thomasmathew.net

UI UX Designer, Web Designer, Freelance Digital Marketing Consultant

Page Load Speed

9.1 sec in total

First Response

1.1 sec

Resources Loaded

7.2 sec

Page Rendered

840 ms

thomasmathew.net screenshot

About Website

Visit thomasmathew.net now to see the best up-to-date Thomasmathew content and also check out these interesting facts you probably never knew about thomasmathew.net

I am a freelance UI/UX Designer and Social Media Manger having expertise as Graphic Designer, WordPress Web Designer, SEO and Digital Marketing Expert who handles multiple projects from USA, India, Qa...

Visit thomasmathew.net

Key Findings

We analyzed Thomasmathew.net page load time and found that the first response time was 1.1 sec and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

thomasmathew.net performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value10.5 s

7/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

thomasmathew.net

1097 ms

wp-emoji-release.min.js

206 ms

style.min.css

412 ms

classic-themes.min.css

610 ms

cursor.css

610 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 88% of them (85 requests) were addressed to the original Thomasmathew.net, 4% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Thomasmathew.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.8 kB (10%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Thomasmathew.net 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 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 148.7 kB

  • Original 178.0 kB
  • After minification 171.7 kB
  • After compression 29.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 148.7 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 107.1 kB

  • Original 2.1 MB
  • After minification 2.0 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. Thomasmathew images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 7.4 kB

  • Original 196.8 kB
  • After minification 196.4 kB
  • After compression 189.4 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

-5%

Potential reduce by 8.6 kB

  • Original 183.8 kB
  • After minification 183.7 kB
  • After compression 175.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. Thomasmathew.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (78%)

Requests Now

82

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thomasmathew.net

thomasmathew.net

1097 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

206 ms

style.min.css

style.min.css

412 ms

classic-themes.min.css

classic-themes.min.css

610 ms

cursor.css

cursor.css

610 ms

chaty-front.min.css

chaty-front.min.css

610 ms

page-visit-counter-public.css

page-visit-counter-public.css

617 ms

font-awesome.min.css

font-awesome.min.css

619 ms

thepostgrid.min.css

thepostgrid.min.css

827 ms

plugins.css

plugins.css

811 ms

cdxn-ig.min.css

cdxn-ig.min.css

811 ms

header-footer-elementor.css

header-footer-elementor.css

813 ms

elementor-icons.min.css

elementor-icons.min.css

820 ms

frontend-legacy.min.css

frontend-legacy.min.css

821 ms

frontend.min.css

frontend.min.css

1218 ms

post-99.css

post-99.css

1016 ms

global.css

global.css

1016 ms

post-913.css

post-913.css

1028 ms

fluent-forms-elementor-widget.css

fluent-forms-elementor-widget.css

1037 ms

frontend.css

frontend.css

1039 ms

post-5742.css

post-5742.css

1222 ms

post-5759.css

post-5759.css

1222 ms

style.css

style.css

1231 ms

dashicons.min.css

dashicons.min.css

1445 ms

style.css

style.css

1454 ms

general.min.css

general.min.css

1418 ms

css

css

34 ms

fontawesome.min.css

fontawesome.min.css

1419 ms

brands.min.css

brands.min.css

1422 ms

solid.min.css

solid.min.css

1434 ms

regular.min.css

regular.min.css

1619 ms

jquery.min.js

jquery.min.js

1826 ms

jquery-migrate.min.js

jquery-migrate.min.js

1626 ms

cht-front-script.min.js

cht-front-script.min.js

1637 ms

page-visit-counter-public.js

page-visit-counter-public.js

1645 ms

js

js

90 ms

animations.min.css

animations.min.css

1652 ms

app.js

app.js

1818 ms

typed.js

typed.js

1953 ms

typed.fe.js

typed.fe.js

1764 ms

yydev-back-to-top.js

yydev-back-to-top.js

1556 ms

priority-menu.js

priority-menu.js

1361 ms

touch-keyboard-navigation.js

touch-keyboard-navigation.js

1459 ms

general.min.js

general.min.js

1460 ms

hoverIntent.min.js

hoverIntent.min.js

1453 ms

maxmegamenu.js

maxmegamenu.js

1449 ms

frontend.js

frontend.js

1260 ms

webpack.runtime.min.js

webpack.runtime.min.js

1293 ms

frontend-modules.min.js

frontend-modules.min.js

1453 ms

waypoints.min.js

waypoints.min.js

1446 ms

core.min.js

core.min.js

1446 ms

swiper.min.js

swiper.min.js

1435 ms

share-link.min.js

share-link.min.js

1254 ms

dialog.min.js

dialog.min.js

1264 ms

frontend.min.js

frontend.min.js

1439 ms

preloaded-modules.min.js

preloaded-modules.min.js

1432 ms

underscore.min.js

underscore.min.js

1429 ms

wp-util.min.js

wp-util.min.js

1252 ms

frontend.min.js

frontend.min.js

1250 ms

TM-logo.jpg

TM-logo.jpg

1220 ms

mackbook-1.png

mackbook-1.png

990 ms

logos-design.jpg

logos-design.jpg

1195 ms

logo-design_2-2.jpg

logo-design_2-2.jpg

1401 ms

healthy-click-uiux-design-3.jpg

healthy-click-uiux-design-3.jpg

1607 ms

police-uiux_2-5.jpg

police-uiux_2-5.jpg

1202 ms

hoxton-web-3.jpg

hoxton-web-3.jpg

1193 ms

grapic-design-4.jpg

grapic-design-4.jpg

2408 ms

Portfolio-2.png

Portfolio-2.png

1600 ms

Portfolio-3.png

Portfolio-3.png

1407 ms

Portfolio-4.png

Portfolio-4.png

1424 ms

Portfolio-1.png

Portfolio-1.png

1607 ms

seo_1-2.jpg

seo_1-2.jpg

1615 ms

seo_2-2.jpg

seo_2-2.jpg

1632 ms

seo_3-2.jpg

seo_3-2.jpg

1928 ms

seo_4-3.jpg

seo_4-3.jpg

1933 ms

Layer-4-1.png

Layer-4-1.png

1730 ms

analytics.js

analytics.js

40 ms

js

js

125 ms

ProximaNovaSoft-Regular.otf

ProximaNovaSoft-Regular.otf

1726 ms

Proxima-Nova-Soft-W03-Regular.ttf

Proxima-Nova-Soft-W03-Regular.ttf

1760 ms

8AD3jaY2BkYGDgAWIxIGZiYARCESBmAfMYAAR6AEMAAAABAAAAANXtRbgAAAAA2AhRFAAAAADYCNuG

8AD3jaY2BkYGDgAWIxIGZiYARCESBmAfMYAAR6AEMAAAABAAAAANXtRbgAAAAA2AhRFAAAAADYCNuG

1 ms

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

54 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

85 ms

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

89 ms

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

90 ms

collect

collect

70 ms

proxima-nova-soft.otf

proxima-nova-soft.otf

1835 ms

fa-brands-400.woff

fa-brands-400.woff

1850 ms

fa-brands-400.woff

fa-brands-400.woff

1891 ms

fa-solid-900.woff

fa-solid-900.woff

2029 ms

fa-solid-900.woff

fa-solid-900.woff

2047 ms

collect

collect

55 ms

fa-regular-400.woff

fa-regular-400.woff

1983 ms

ga-audiences

ga-audiences

75 ms

fa-regular-400.woff

fa-regular-400.woff

1897 ms

Path-111042.svg

Path-111042.svg

1628 ms

print.css

print.css

208 ms

Accessibility Review

thomasmathew.net accessibility score

84

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

ARIA progressbar elements do not have accessible names.

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.

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

thomasmathew.net 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

SEO Factors

thomasmathew.net SEO score

88

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

thomasmathew.net

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