Access feyverly.com. Home – Corporate

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.149

76/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

feyverly.com

56 ms

feyverly.com

1695 ms

gtm.js

138 ms

js

282 ms

172 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 53% of them (28 requests) were addressed to the original Feyverly.com, 17% (9 requests) were made to Googletagmanager.com and 6% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Googletagmanager.com.

Content Size

834.7 kB

After Optimization

587.8 kB

In fact, the total size of Feyverly.com main page is 834.7 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. 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. Javascripts take 498.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 243.5 kB

Original 287.1 kB
After minification 278.7 kB
After compression 43.6 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 243.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 12.2 kB
After minification 12.2 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. Feyverly images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

Original 498.8 kB
After minification 498.8 kB
After compression 495.5 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

-0%

Potential reduce by 46 B

Original 36.5 kB
After minification 36.5 kB
After compression 36.5 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. Feyverly.com has all CSS files already compressed.

Requests Now

After Optimization

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

Accessibility Issues

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-*] attributes do not match their roles

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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

TH
Language Claimed

EN
Encoding

UTF-8

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

feyverly.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home – Corporate - Feyverly

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

feyverly.com

feyverly.com

gtm.js

js

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

feyverly.com

feyverly.com

gtm.js

js

css

style.min.css

style.min.css

style.min.css

dashicons.min.css

jquery.min.js

script.min.js

modernizr.js

js

js

email-decode.min.js

bilmur.min.js

gtm4wp-form-move-tracker.js

main.js

e-202410.js

punycode.min.js

utils.min.js

wpforms.min.js

api.js

js

js

gtm.js

ga.js

js

Feyverlylogo.jpg

businessman-using-smart-devices-for-digital-techno-2022-10-25-10-10-36-utc-min.webp

young-carefree-brunette-girls-friends-in-casual-wi-2021-08-27-09-25-17-utc-min.webp

Home-IMG-4.jpg

businessman-building-a-successful-financial-graph-2021-08-26-22-39-46-utc-min.webp

Home-CTA.jpg

submit-spin.svg

5aU19_a8oxmIfJpbERySiBhc9V0.ttf

5aU69_a8oxmIdGl4ATGwgDI.ttf

5aU19_a8oxmIfLZcERySiBhc9V0.ttf

tatsu-icons.ttf

__utm.gif

analytics.js

destination

collect

ga-audiences