Tools & Wizards About Us
sweeto.com.tr screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

sweeto.com.tr

Welcome to Sweeto Confectionery World

Page Load Speed

13.8 sec in total

First Response

2.6 sec

Resources Loaded

10.8 sec

Page Rendered

368 ms

sweeto.com.tr screenshot

About Website

Welcome to sweeto.com.tr homepage info - get ready to check Sweeto best content right away, or after learning these important things about sweeto.com.tr

Visit sweeto.com.tr

Key Findings

We analyzed Sweeto.com.tr page load time and found that the first response time was 2.6 sec and then it took 11.1 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

sweeto.com.tr performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

www.sweeto.com.tr

2639 ms

css

25 ms

global.css

135 ms

bootstrap-light.min.css

270 ms

base.min.css

404 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 94% of them (100 requests) were addressed to the original Sweeto.com.tr, 4% (4 requests) were made to Fonts.googleapis.com and 1% (1 request) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Sweeto.com.tr.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.7 kB (11%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweeto.com.tr main page is 1.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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 116.2 kB

  • Original 140.3 kB
  • After minification 135.4 kB
  • After compression 24.2 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 116.2 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 70.8 kB

  • Original 1.2 MB
  • After minification 1.1 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. Sweeto images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.7 kB

  • Original 293.0 kB
  • After minification 293.0 kB
  • After compression 289.3 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

-4%

Potential reduce by 5.1 kB

  • Original 119.2 kB
  • After minification 119.2 kB
  • After compression 114.1 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. Sweeto.com.tr has all CSS files already compressed.

Requests Breakdown

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

Requests Now

103

After Optimization

23

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.sweeto.com.tr

www.sweeto.com.tr

2639 ms

css

css

25 ms

global.css

global.css

135 ms

bootstrap-light.min.css

bootstrap-light.min.css

270 ms

base.min.css

base.min.css

404 ms

woo-widget-price-filter.min.css

woo-widget-price-filter.min.css

395 ms

style.min.css

style.min.css

535 ms

js_composer.min.css

js_composer.min.css

668 ms

pum-site-styles.css

pum-site-styles.css

406 ms

header-boxed.min.css

header-boxed.min.css

407 ms

widget-recent-post-comments.min.css

widget-recent-post-comments.min.css

545 ms

widget-wd-recent-posts.min.css

widget-wd-recent-posts.min.css

548 ms

widget-nav.min.css

widget-nav.min.css

558 ms

woo-widget-wd-layered-nav.min.css

woo-widget-wd-layered-nav.min.css

555 ms

woo-mod-swatches-base.min.css

woo-mod-swatches-base.min.css

681 ms

woo-mod-swatches-filter.min.css

woo-mod-swatches-filter.min.css

681 ms

woo-widget-layered-nav-stock-status.min.css

woo-widget-layered-nav-stock-status.min.css

687 ms

woo-widget-product-list.min.css

woo-widget-product-list.min.css

694 ms

woo-widget-slider-price-filter.min.css

woo-widget-slider-price-filter.min.css

693 ms

wp-gutenberg.min.css

wp-gutenberg.min.css

800 ms

int-wpcf7.min.css

int-wpcf7.min.css

801 ms

int-rev-slider.min.css

int-rev-slider.min.css

806 ms

base-deprecated.min.css

base-deprecated.min.css

819 ms

int-wpb-base.min.css

int-wpb-base.min.css

829 ms

int-wpb-base-deprecated.min.css

int-wpb-base-deprecated.min.css

827 ms

woocommerce-base.min.css

woocommerce-base.min.css

937 ms

mod-star-rating.min.css

mod-star-rating.min.css

934 ms

woo-el-track-order.min.css

woo-el-track-order.min.css

937 ms

woo-gutenberg.min.css

woo-gutenberg.min.css

951 ms

header-base.min.css

header-base.min.css

958 ms

mod-tools.min.css

mod-tools.min.css

960 ms

el-section-title.min.css

el-section-title.min.css

1069 ms

mod-highlighted-text.min.css

mod-highlighted-text.min.css

1070 ms

header-el-base.min.css

header-el-base.min.css

1070 ms

el-row-divider.min.css

el-row-divider.min.css

1083 ms

el-text-block.min.css

el-text-block.min.css

1088 ms

el-counter.min.css

el-counter.min.css

1092 ms

css

css

20 ms

css

css

19 ms

lib-owl-carousel.min.css

lib-owl-carousel.min.css

1201 ms

blog-base.min.css

blog-base.min.css

1078 ms

blog-loop-base-old.min.css

blog-loop-base-old.min.css

941 ms

blog-loop-design-mask.min.css

blog-loop-design-mask.min.css

828 ms

footer-base.min.css

footer-base.min.css

821 ms

css

css

15 ms

el-social-icons.min.css

el-social-icons.min.css

826 ms

opt-sticky-social.min.css

opt-sticky-social.min.css

935 ms

xts-header_941270-1706130654.css

xts-header_941270-1706130654.css

804 ms

xts-theme_settings_default-1705239702.css

xts-theme_settings_default-1705239702.css

802 ms

rs6.css

rs6.css

811 ms

jquery.min.js

jquery.min.js

936 ms

jquery-migrate.min.js

jquery-migrate.min.js

807 ms

circle-progress.js

circle-progress.js

794 ms

global.js

global.js

794 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

799 ms

add-to-cart.min.js

add-to-cart.min.js

817 ms

js.cookie.min.js

js.cookie.min.js

811 ms

woocommerce.min.js

woocommerce.min.js

918 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

816 ms

device.min.js

device.min.js

815 ms

updateCartFragmentsFix.js

updateCartFragmentsFix.js

825 ms

index.js

index.js

812 ms

index.js

index.js

832 ms

rbtools.min.js

rbtools.min.js

1170 ms

rs6.min.js

rs6.min.js

950 ms

js_composer_front.min.js

js_composer_front.min.js

829 ms

core.min.js

core.min.js

830 ms

pum-site-scripts.js

pum-site-scripts.js

816 ms

helpers.min.js

helpers.min.js

841 ms

woocommerceNotices.min.js

woocommerceNotices.min.js

928 ms

scrollBar.min.js

scrollBar.min.js

823 ms

headerBuilder.min.js

headerBuilder.min.js

823 ms

menuOffsets.min.js

menuOffsets.min.js

830 ms

menuSetUp.min.js

menuSetUp.min.js

934 ms

waypoints.min.js

waypoints.min.js

930 ms

counter.min.js

counter.min.js

930 ms

imagesloaded.min.js

imagesloaded.min.js

819 ms

owl.carousel.min.js

owl.carousel.min.js

831 ms

owlCarouselInit.min.js

owlCarouselInit.min.js

926 ms

isotope-bundle.min.js

isotope-bundle.min.js

946 ms

masonryLayout.min.js

masonryLayout.min.js

932 ms

mobileNavigation.min.js

mobileNavigation.min.js

933 ms

stickySocialButtons.min.js

stickySocialButtons.min.js

825 ms

Fora-Sweets-Logo.png

Fora-Sweets-Logo.png

682 ms

Marshmallow-02-1.jpg

Marshmallow-02-1.jpg

660 ms

Licorice-1.jpg

Licorice-1.jpg

795 ms

jelly-1.jpg

jelly-1.jpg

673 ms

dummy.png

dummy.png

674 ms

sertifika-1.jpg

sertifika-1.jpg

677 ms

ISM-Koln-350x250.jpg

ISM-Koln-350x250.jpg

780 ms

Prodexpo-350x250.jpg

Prodexpo-350x250.jpg

803 ms

Sweets-Snacks-350x250.jpg

Sweets-Snacks-350x250.jpg

805 ms

Alimentec-350x250.jpg

Alimentec-350x250.jpg

812 ms

PLMA-Hollanda-350x250.jpg

PLMA-Hollanda-350x250.jpg

820 ms

WorldFood-350x250.jpg

WorldFood-350x250.jpg

913 ms

YZB-350x250.jpg

YZB-350x250.jpg

921 ms

Sial-350x250.jpg

Sial-350x250.jpg

924 ms

876308834

876308834

98 ms

ISM-Middle-East-350x250.jpg

ISM-Middle-East-350x250.jpg

900 ms

font

font

91 ms

Thaifex-264x300.jpg

Thaifex-264x300.jpg

908 ms

Sweets-Snacks-00-264x300.jpg

Sweets-Snacks-00-264x300.jpg

807 ms

ISM-COLOGNE-264x300.jpg

ISM-COLOGNE-264x300.jpg

900 ms

ISM-Japan-264x300.jpg

ISM-Japan-264x300.jpg

885 ms

Sweeto-Strawberry-Marshmallow.jpg

Sweeto-Strawberry-Marshmallow.jpg

1540 ms

old-about-us-bg-2.jpg

old-about-us-bg-2.jpg

1059 ms

Accessibility Review

sweeto.com.tr accessibility score

87

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

sweeto.com.tr 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sweeto.com.tr SEO score

93

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

sweeto.com.tr

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