Tools & Wizards About Us
webcazine.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

webcazine.com

WebCazine.com - Dunia Gadget Indonesia

Page Load Speed

12.5 sec in total

First Response

90 ms

Resources Loaded

12.2 sec

Page Rendered

201 ms

webcazine.com screenshot

About Website

Click here to check amazing Web Cazine content for India. Otherwise, check out these important facts you probably never knew about webcazine.com

Temukan Bermacam-macam jenis gadget terbaru, ulasan gadget, berita terkini, dan tips terbaik seputar gadget di WebCazine.com.

Visit webcazine.com

Key Findings

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

Performance Metrics

webcazine.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value3,390 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

webcazine.com

90 ms

www.fonguide.com

3014 ms

siteground-optimizer-combined-css-c6afc36fda8e010ebc566d8dab9a28c8.css

825 ms

css

62 ms

jquery.min.js

1409 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webcazine.com, 55% (46 requests) were made to Fonguide.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Fonguide.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.5 kB (12%)

Content Size

1.1 MB

After Optimization

978.2 kB

  • HTML
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 72.3 kB

  • Original 93.8 kB
  • After minification 93.0 kB
  • After compression 21.5 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 72.3 kB or 77% of the original size.

JavaScript Optimization

-7%

Potential reduce by 64.2 kB

  • Original 961.6 kB
  • After minification 961.6 kB
  • After compression 897.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 0 B

  • Original 59.2 kB
  • After minification 59.2 kB
  • After compression 59.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. Webcazine.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 60 (80%)

Requests Now

75

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webcazine.com

webcazine.com

90 ms

www.fonguide.com

www.fonguide.com

3014 ms

siteground-optimizer-combined-css-c6afc36fda8e010ebc566d8dab9a28c8.css

siteground-optimizer-combined-css-c6afc36fda8e010ebc566d8dab9a28c8.css

825 ms

css

css

62 ms

jquery.min.js

jquery.min.js

1409 ms

jquery-migrate.min.js

jquery-migrate.min.js

1750 ms

cmtoc-jquery-foldable.min.js

cmtoc-jquery-foldable.min.js

2305 ms

cmtoc-frontend-js.min.js

cmtoc-frontend-js.min.js

3270 ms

cookie-law-info.min.js

cookie-law-info.min.js

3919 ms

swiper-bundle.min.js

swiper-bundle.min.js

4448 ms

wpswiper-frontend-js.min.js

wpswiper-frontend-js.min.js

6303 ms

js

js

78 ms

eventMove.min.js

eventMove.min.js

5704 ms

fancybox.min.js

fancybox.min.js

5643 ms

bafg_twentytwenty.min.js

bafg_twentytwenty.min.js

5772 ms

adsbygoogle.js

adsbygoogle.js

147 ms

www.fonguide.com

www.fonguide.com

5829 ms

adsbygoogle.js

adsbygoogle.js

288 ms

api.js

api.js

72 ms

adsbygoogle.js

adsbygoogle.js

243 ms

lazysizes.min.js

lazysizes.min.js

6460 ms

hoverIntent.min.js

hoverIntent.min.js

6695 ms

superfish.min.js

superfish.min.js

6441 ms

superfish.args.min.js

superfish.args.min.js

6695 ms

skip-links.min.js

skip-links.min.js

6581 ms

responsive-menus.min.js

responsive-menus.min.js

6694 ms

genesis-sample.min.js

genesis-sample.min.js

7012 ms

e-202424.js

e-202424.js

42 ms

bafg_custom_js.min.js

bafg_custom_js.min.js

7039 ms

jquery.toastmessage.js

jquery.toastmessage.js

7071 ms

core.min.js

core.min.js

7202 ms

mouse.min.js

mouse.min.js

7559 ms

resizable.min.js

resizable.min.js

7582 ms

draggable.min.js

draggable.min.js

7275 ms

controlgroup.min.js

controlgroup.min.js

7996 ms

checkboxradio.min.js

checkboxradio.min.js

7381 ms

button.min.js

button.min.js

7579 ms

dialog.min.js

dialog.min.js

7721 ms

suggest.min.js

suggest.min.js

7771 ms

utils.min.js

utils.min.js

7948 ms

script.js

script.js

7876 ms

test-ajax.js

test-ajax.js

7990 ms

quicktags.min.js

quicktags.min.js

8279 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

8136 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

8245 ms

wp-polyfill.min.js

wp-polyfill.min.js

7562 ms

hooks.min.js

hooks.min.js

7004 ms

analytics.js

analytics.js

85 ms

show_ads_impl.js

show_ads_impl.js

270 ms

i18n.min.js

i18n.min.js

6479 ms

collect

collect

14 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf

19 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf

21 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf

22 ms

S81d539a47bef4b5c9ab931ed11596c68n.jpg_350x350.jpg

S81d539a47bef4b5c9ab931ed11596c68n.jpg_350x350.jpg

413 ms

collect

collect

31 ms

js

js

16 ms

zrt_lookup.html

zrt_lookup.html

32 ms

ads

ads

170 ms

common.min.js

common.min.js

6212 ms

ca-pub-7219917511588466

ca-pub-7219917511588466

80 ms

dom-ready.min.js

dom-ready.min.js

5481 ms

a11y.min.js

a11y.min.js

4744 ms

wplink.min.js

wplink.min.js

4007 ms

menu.min.js

menu.min.js

3383 ms

autocomplete.min.js

autocomplete.min.js

3348 ms

ads

ads

569 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDc.ttf

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDc.ttf

13 ms

recaptcha__en.js

recaptcha__en.js

102 ms

S81d539a47bef4b5c9ab931ed11596c68n.jpg_350x350.jpg

S81d539a47bef4b5c9ab931ed11596c68n.jpg_350x350.jpg

88 ms

esxXyxhM04I

esxXyxhM04I

178 ms

ads

ads

497 ms

www-player.css

www-player.css

9 ms

www-embed-player.js

www-embed-player.js

38 ms

base.js

base.js

64 ms

ad_status.js

ad_status.js

174 ms

jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js

jj2eNDzr7OxRmG3eEZdf1bHpefYrrxl4VJQY9raQMR0.js

101 ms

embed.js

embed.js

54 ms

id

id

19 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

19 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

20 ms

Create

Create

110 ms

GenerateIT

GenerateIT

15 ms

log_event

log_event

16 ms

Accessibility Review

webcazine.com accessibility score

83

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.

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

webcazine.com SEO score

78

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

webcazine.com

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