Tools & Wizards About Us
awethemes.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

awethemes.com

AweThemes

Page Load Speed

1.1 sec in total

First Response

108 ms

Resources Loaded

534 ms

Page Rendered

499 ms

awethemes.com screenshot

About Website

Visit awethemes.com now to see the best up-to-date Awe Themes content for Turkey and also check out these interesting facts you probably never knew about awethemes.com

Visit awethemes.com

Key Findings

We analyzed Awethemes.com page load time and found that the first response time was 108 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

awethemes.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.5 s

100/100

10%

Network Requests Diagram

awethemes.com

108 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

20 ms

css_TmPSVSaROgWR_-YGJVHt9DidvtCx6wWMf9Ykyo0XpYc.css

21 ms

css_Wu8npAzy16WmnnnWKxpexfgsAryolGGaX6yO3GWA5bU.css

22 ms

css_HDoeH-iabYbNaPwe3k8ib-DwzPirZNNSozQZaVCxr4Y.css

29 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 97% of them (30 requests) were addressed to the original Awethemes.com, 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (357 ms) belongs to the original domain Awethemes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.6 kB (24%)

Content Size

911.8 kB

After Optimization

694.1 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Awethemes.com main page is 911.8 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. 55% of websites need less resources to load. Images take 647.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.1 kB

  • Original 18.8 kB
  • After minification 18.8 kB
  • After compression 4.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 14.1 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 117 B

  • Original 647.0 kB
  • After minification 646.9 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. Awe Themes images are well optimized though.

CSS Optimization

-83%

Potential reduce by 203.4 kB

  • Original 246.0 kB
  • After minification 245.2 kB
  • After compression 42.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. Awethemes.com needs all CSS files to be minified and compressed as it can save up to 203.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (37%)

Requests Now

30

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

awethemes.com

awethemes.com

108 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

20 ms

css_TmPSVSaROgWR_-YGJVHt9DidvtCx6wWMf9Ykyo0XpYc.css

css_TmPSVSaROgWR_-YGJVHt9DidvtCx6wWMf9Ykyo0XpYc.css

21 ms

css_Wu8npAzy16WmnnnWKxpexfgsAryolGGaX6yO3GWA5bU.css

css_Wu8npAzy16WmnnnWKxpexfgsAryolGGaX6yO3GWA5bU.css

22 ms

css_HDoeH-iabYbNaPwe3k8ib-DwzPirZNNSozQZaVCxr4Y.css

css_HDoeH-iabYbNaPwe3k8ib-DwzPirZNNSozQZaVCxr4Y.css

29 ms

jquery.min.js

jquery.min.js

92 ms

jquery.once.js

jquery.once.js

14 ms

drupal.js

drupal.js

14 ms

jquery.owl.carousel.min.js

jquery.owl.carousel.min.js

118 ms

jquery.nav.js

jquery.nav.js

90 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

109 ms

scripts.js

scripts.js

109 ms

modernizr.js

modernizr.js

113 ms

logo.png

logo.png

110 ms

pradise-t.jpg

pradise-t.jpg

111 ms

hosoren-t.jpg

hosoren-t.jpg

112 ms

hillter-t.jpg

hillter-t.jpg

357 ms

thefamly-t.jpg

thefamly-t.jpg

113 ms

orenmode-t.jpg

orenmode-t.jpg

112 ms

ambrosia-t.jpg

ambrosia-t.jpg

113 ms

gtm.js

gtm.js

277 ms

image-1.jpg

image-1.jpg

272 ms

product-overlay.png

product-overlay.png

268 ms

bg-front-center.jpg

bg-front-center.jpg

270 ms

img-blog-thumb.jpg

img-blog-thumb.jpg

272 ms

proximanova-regular.woff

proximanova-regular.woff

270 ms

proximanova-bold.woff

proximanova-bold.woff

103 ms

proximanova-light.woff

proximanova-light.woff

102 ms

awe-font.woff

awe-font.woff

105 ms

font-awesome.woff

font-awesome.woff

106 ms

proximanova-semibold.woff

proximanova-semibold.woff

103 ms

Accessibility Review

awethemes.com accessibility score

96

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

awethemes.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

awethemes.com SEO score

91

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awethemes.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Awethemes.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

awethemes.com

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