Tools & Wizards About Us
funntaste.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

funntaste.com

Fun N' Taste - Food & Places Guide For Malaysians

Page Load Speed

5.9 sec in total

First Response

648 ms

Resources Loaded

4.8 sec

Page Rendered

473 ms

funntaste.com screenshot

About Website

Welcome to funntaste.com homepage info - get ready to check Fun N Taste best content for Malaysia right away, or after learning these important things about funntaste.com

We're an independent media publisher that curates easily-consumable Food, Travel and Things To Do content. We're based in Malaysia.

Visit funntaste.com

Key Findings

We analyzed Funntaste.com page load time and found that the first response time was 648 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

funntaste.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.2 s

41/100

10%

Network Requests Diagram

funntaste.com

648 ms

funntaste.com

390 ms

js

65 ms

a5ff7.css

116 ms

14d31.css

236 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 15% of them (15 requests) were addressed to the original Funntaste.com, 10% (10 requests) were made to Static.xx.fbcdn.net and 10% (10 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (649 ms) relates to the external source Securepubads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 463.3 kB (31%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Funntaste.com main page is 1.5 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. 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 90.1 kB

  • Original 114.8 kB
  • After minification 114.8 kB
  • After compression 24.8 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 90.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 7.6 kB

  • Original 145.0 kB
  • After minification 137.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. Fun N Taste images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 365.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 744.2 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 365.4 kB or 33% of the original size.

CSS Optimization

-0%

Potential reduce by 256 B

  • Original 147.1 kB
  • After minification 147.1 kB
  • After compression 146.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. Funntaste.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 62 (72%)

Requests Now

86

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

funntaste.com

funntaste.com

648 ms

funntaste.com

funntaste.com

390 ms

js

js

65 ms

a5ff7.css

a5ff7.css

116 ms

14d31.css

14d31.css

236 ms

3fa0b.css

3fa0b.css

361 ms

c45ba.js

c45ba.js

246 ms

ats.js

ats.js

233 ms

adsbygoogle.js

adsbygoogle.js

74 ms

js

js

66 ms

sdk.js

sdk.js

42 ms

55015.css

55015.css

245 ms

deb40.js

deb40.js

191 ms

505f8.js

505f8.js

192 ms

0aa88.js

0aa88.js

299 ms

fa2cc.js

fa2cc.js

240 ms

50dd5.js

50dd5.js

250 ms

06bbb.js

06bbb.js

423 ms

gpt.js

gpt.js

100 ms

FP-390x220.jpg

FP-390x220.jpg

185 ms

show_ads_impl.js

show_ads_impl.js

126 ms

tielabs-fonticon.ttf

tielabs-fonticon.ttf

131 ms

pubads_impl.js

pubads_impl.js

67 ms

sdk.js

sdk.js

80 ms

zrt_lookup.html

zrt_lookup.html

89 ms

ads

ads

110 ms

sdk.js

sdk.js

91 ms

webfont.js

webfont.js

124 ms

esp.js

esp.js

139 ms

sync.min.js

sync.min.js

133 ms

publishertag.ids.js

publishertag.ids.js

147 ms

uid2SecureSignal.js

uid2SecureSignal.js

144 ms

ob.js

ob.js

165 ms

pubcid.min.js

pubcid.min.js

146 ms

esp.js

esp.js

164 ms

ads

ads

649 ms

container.html

container.html

142 ms

css

css

129 ms

map

map

154 ms

sodar

sodar

71 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

38 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

51 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

72 ms

page.php

page.php

170 ms

sodar2.js

sodar2.js

60 ms

runner.html

runner.html

30 ms

aframe

aframe

74 ms

esp

esp

50 ms

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

awBj2nEM4FjaFk3wlyC-mA9dnmiUMLTOhjF5f4M09mQ.js

25 ms

lFC1eVji7gN.css

lFC1eVji7gN.css

37 ms

dvL-mSr_f6M.js

dvL-mSr_f6M.js

49 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

48 ms

FsgTKAP125G.js

FsgTKAP125G.js

88 ms

pLoSlJD7y1F.js

pLoSlJD7y1F.js

91 ms

Glud--w-qOK.js

Glud--w-qOK.js

97 ms

l8Qk4nS2o1N.js

l8Qk4nS2o1N.js

87 ms

p55HfXW__mM.js

p55HfXW__mM.js

87 ms

pd

pd

164 ms

290950674_1688006854897167_2926030652409566253_n.jpg

290950674_1688006854897167_2926030652409566253_n.jpg

139 ms

yhMLxgtMNUo.js

yhMLxgtMNUo.js

35 ms

339132210_1146757339296019_6082496811561886274_n.png

339132210_1146757339296019_6082496811561886274_n.png

131 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

33 ms

df16168f-8821-eed2-dab4-97a884454c7d

df16168f-8821-eed2-dab4-97a884454c7d

150 ms

pixel

pixel

338 ms

pixel

pixel

337 ms

gen_204

gen_204

287 ms

pixel

pixel

63 ms

8964552396074085254

8964552396074085254

332 ms

icon.png

icon.png

54 ms

abg_lite.js

abg_lite.js

74 ms

omrhp.js

omrhp.js

81 ms

Q12zgMmT.js

Q12zgMmT.js

45 ms

window_focus.js

window_focus.js

65 ms

cookie_push_onload.html

cookie_push_onload.html

79 ms

qs_click_protection.js

qs_click_protection.js

72 ms

ufs_web_display.js

ufs_web_display.js

83 ms

page.php

page.php

234 ms

62bHydCX.html

62bHydCX.html

145 ms

dcm

dcm

238 ms

gp_match

gp_match

296 ms

290950674_1688006854897167_2926030652409566253_n.jpg

290950674_1688006854897167_2926030652409566253_n.jpg

71 ms

sd

sd

145 ms

339132210_1146757339296019_6082496811561886274_n.png

339132210_1146757339296019_6082496811561886274_n.png

105 ms

sd

sd

127 ms

pixel

pixel

23 ms

pixel

pixel

26 ms

pixel

pixel

24 ms

bounce

bounce

51 ms

rum

rum

52 ms

pixel

pixel

19 ms

sync

sync

22 ms

pixel

pixel

67 ms

rum

rum

25 ms

pixel

pixel

23 ms

activeview

activeview

73 ms

pixel

pixel

14 ms

pixel

pixel

14 ms

Accessibility Review

funntaste.com accessibility score

85

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-hidden="true"] elements contain focusable descendents

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

funntaste.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

funntaste.com SEO score

85

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

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 Funntaste.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 Funntaste.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

funntaste.com

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