Tools & Wizards About Us
antikan.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

antikan.com

antikan.com Satılık Antika Pazarı ,

Page Load Speed

14.3 sec in total

First Response

47 ms

Resources Loaded

14.1 sec

Page Rendered

250 ms

antikan.com screenshot

About Website

Click here to check amazing Antika N content for Turkey. Otherwise, check out these important facts you probably never knew about antikan.com

antikan.com Türkiyede antika almak ve satmak isteyenlerin buluştuğu web sitesi

Visit antikan.com

Key Findings

We analyzed Antikan.com page load time and found that the first response time was 47 ms and then it took 14.3 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

antikan.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

antikan.com

47 ms

antikan.com

5878 ms

project1.css

1094 ms

buttons.css

1106 ms

jquery-ui.css

22 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 42% of them (42 requests) were addressed to the original Antikan.com, 13% (13 requests) were made to Pagead2.googlesyndication.com and 10% (10 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6.5 sec) belongs to the original domain Antikan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.9 kB (7%)

Content Size

4.0 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Antikan.com main page is 4.0 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. 80% 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. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 57.9 kB

  • Original 66.7 kB
  • After minification 61.4 kB
  • After compression 8.9 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 57.9 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 220.2 kB

  • Original 3.7 MB
  • After minification 3.5 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. Antika N images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.1 kB

  • Original 279.5 kB
  • After minification 279.5 kB
  • After compression 274.4 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

-25%

Potential reduce by 1.7 kB

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.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. Antikan.com needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (61%)

Requests Now

92

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

antikan.com

antikan.com

47 ms

antikan.com

antikan.com

5878 ms

project1.css

project1.css

1094 ms

buttons.css

buttons.css

1106 ms

jquery-ui.css

jquery-ui.css

22 ms

jquery.fancybox.css

jquery.fancybox.css

1115 ms

jquery.min.js

jquery.min.js

26 ms

jquery-ui.min.js

jquery-ui.min.js

36 ms

ajax.js

ajax.js

1652 ms

jquery.fancybox.js

jquery.fancybox.js

1161 ms

lightbox.css

lightbox.css

1162 ms

adsbygoogle.js

adsbygoogle.js

360 ms

adsbygoogle.js

adsbygoogle.js

554 ms

m02_top.png

m02_top.png

80 ms

logo1.png

logo1.png

80 ms

palatattoo-banner.jpg

palatattoo-banner.jpg

80 ms

m02.gif

m02.gif

80 ms

menu0_01.png

menu0_01.png

79 ms

menu0_02.png

menu0_02.png

95 ms

menu0_03.png

menu0_03.png

97 ms

m13.gif

m13.gif

628 ms

m17.gif

m17.gif

95 ms

m25.gif

m25.gif

97 ms

m19.gif

m19.gif

95 ms

m20.gif

m20.gif

632 ms

loading.gif

loading.gif

104 ms

plus.png

plus.png

104 ms

bg1.png

bg1.png

139 ms

bg1_top.png

bg1_top.png

105 ms

thumb_2851_1.jpg

thumb_2851_1.jpg

141 ms

thumb_2850_1.jpg

thumb_2850_1.jpg

139 ms

thumb_2849_1.jpg

thumb_2849_1.jpg

142 ms

thumb_2848_1.jpg

thumb_2848_1.jpg

148 ms

thumb_2847_1.jpg

thumb_2847_1.jpg

141 ms

thumb_2846_1.jpg

thumb_2846_1.jpg

142 ms

thumb_2845_1.jpg

thumb_2845_1.jpg

6457 ms

thumb_2844_1.jpg

thumb_2844_1.jpg

153 ms

thumb_2843_1.jpg

thumb_2843_1.jpg

159 ms

thumb_2842_1.jpg

thumb_2842_1.jpg

162 ms

thumb_2841_1.jpg

thumb_2841_1.jpg

183 ms

thumb_2840_1.jpg

thumb_2840_1.jpg

184 ms

thumb_2839_1.jpg

thumb_2839_1.jpg

185 ms

thumb_2838_1.jpg

thumb_2838_1.jpg

186 ms

thumb_2837_1.jpg

thumb_2837_1.jpg

192 ms

thumb_2833_1.jpg

thumb_2833_1.jpg

187 ms

spacer.gif

spacer.gif

202 ms

show_ads_impl.js

show_ads_impl.js

293 ms

btn_back.jpg

btn_back.jpg

112 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

12 ms

zrt_lookup.html

zrt_lookup.html

41 ms

ads

ads

225 ms

ads

ads

169 ms

ads

ads

224 ms

ads

ads

232 ms

reactive_library.js

reactive_library.js

362 ms

ca-pub-9570970845193816

ca-pub-9570970845193816

98 ms

pixel

pixel

68 ms

dv3.js

dv3.js

164 ms

window_focus.js

window_focus.js

24 ms

qs_click_protection.js

qs_click_protection.js

28 ms

ufs_web_display.js

ufs_web_display.js

28 ms

gen_204

gen_204

81 ms

pixel

pixel

75 ms

pixel

pixel

73 ms

setuid

setuid

47 ms

rum

rum

20 ms

pixel

pixel

13 ms

rum

rum

48 ms

pixel

pixel

22 ms

ad

ad

38 ms

7933748893645157338

7933748893645157338

165 ms

abg_lite.js

abg_lite.js

108 ms

omrhp.js

omrhp.js

108 ms

dcm

dcm

183 ms

ca

ca

155 ms

Q12zgMmT.js

Q12zgMmT.js

108 ms

icon.png

icon.png

23 ms

62bHydCX.html

62bHydCX.html

24 ms

pixel

pixel

137 ms

ad

ad

41 ms

activeview

activeview

197 ms

gen_204

gen_204

200 ms

ttep1hf2xTKPY5HV4abLvqDFRXZuZQmhABAIUKmOBs4.js

ttep1hf2xTKPY5HV4abLvqDFRXZuZQmhABAIUKmOBs4.js

3 ms

14342567963103880252

14342567963103880252

85 ms

dcm

dcm

151 ms

DsR2kPoxtp.gif

DsR2kPoxtp.gif

153 ms

ca

ca

79 ms

pixel

pixel

75 ms

pixel

pixel

75 ms

activeview

activeview

74 ms

rum

rum

30 ms

setuid

setuid

141 ms

pixel

pixel

15 ms

rum

rum

29 ms

pixel

pixel

24 ms

src=13452495;type=invmedia;cat=avla30;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=;gdpr_consent=;ord=1

src=13452495;type=invmedia;cat=avla30;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=;gdpr_consent=;ord=1

79 ms

st1

st1

25 ms

get

get

18 ms

st1

st1

6 ms

Accessibility Review

antikan.com accessibility score

62

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.

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

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

antikan.com best practices score

58

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

antikan.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antikan.com can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Antikan.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

antikan.com

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