Tools & Wizards About Us
vamp.gr screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

vamp.gr

Πυτζάμες, Νυχτικά, Φορέματα Θαλάσσης και Εσώρουχα για Άνδρες και Γυναίκες Vamp Fashion

Page Load Speed

3.8 sec in total

First Response

627 ms

Resources Loaded

3 sec

Page Rendered

228 ms

vamp.gr screenshot

About Website

Welcome to vamp.gr homepage info - get ready to check Vamp best content for Greece right away, or after learning these important things about vamp.gr

Ανακαλύψτε Υψηλής Ποιότητας Πυτζάμες, Νυχτικά και Φορέματα Θαλάσσης. Κατασκευασμένα από 100% φυσικά υλικά. Αποστολή σε όλη την Ελλάδα.

Visit vamp.gr

Key Findings

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

Performance Metrics

vamp.gr performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value24,110 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.581

11/100

15%

TTI (Time to Interactive)

Value41.1 s

0/100

10%

Network Requests Diagram

vamp.gr

627 ms

www.vamp.gr

643 ms

menu.gkmenu.css

95 ms

meyer.css

189 ms

layout.css

189 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 87% of them (26 requests) were addressed to the original Vamp.gr, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (870 ms) belongs to the original domain Vamp.gr.

Page Optimization Overview & Recommendations

Page size can be reduced by 394.3 kB (34%)

Content Size

1.2 MB

After Optimization

775.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vamp.gr main page is 1.2 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. 30% of websites need less resources to load. Images take 633.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.8 kB

  • Original 25.9 kB
  • After minification 25.1 kB
  • After compression 7.1 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 18.8 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 10.0 kB

  • Original 633.4 kB
  • After minification 623.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. Vamp images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 262.5 kB

  • Original 382.8 kB
  • After minification 371.8 kB
  • After compression 120.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 262.5 kB or 69% of the original size.

CSS Optimization

-80%

Potential reduce by 103.1 kB

  • Original 128.0 kB
  • After minification 105.2 kB
  • After compression 25.0 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. Vamp.gr needs all CSS files to be minified and compressed as it can save up to 103.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (70%)

Requests Now

27

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vamp. 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 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vamp.gr

vamp.gr

627 ms

www.vamp.gr

www.vamp.gr

643 ms

menu.gkmenu.css

menu.gkmenu.css

95 ms

meyer.css

meyer.css

189 ms

layout.css

layout.css

189 ms

joomla.css

joomla.css

195 ms

template.css

template.css

200 ms

menu.css

menu.css

193 ms

gk.stuff.css

gk.stuff.css

197 ms

k2.css

k2.css

282 ms

redshop.css

redshop.css

286 ms

typography.style1.css

typography.style1.css

289 ms

style1.css

style1.css

295 ms

module_default.css

module_default.css

297 ms

mootools-core.js

mootools-core.js

394 ms

core.js

core.js

374 ms

caption.js

caption.js

374 ms

mootools-more.js

mootools-more.js

683 ms

menu.gkmenu.js

menu.gkmenu.js

383 ms

gk.scripts.js

gk.scripts.js

384 ms

acymailing_module.js

acymailing_module.js

468 ms

css

css

26 ms

ga.js

ga.js

41 ms

logo_light.png

logo_light.png

96 ms

search.png

search.png

96 ms

vamp-pyjamas-summer-2016.jpg

vamp-pyjamas-summer-2016.jpg

870 ms

social_bg.png

social_bg.png

98 ms

social_icons.png

social_icons.png

98 ms

__utm.gif

__utm.gif

17 ms

all.js

all.js

8 ms

Accessibility Review

vamp.gr accessibility score

78

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

[role]s are not contained by their required parent element

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

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

vamp.gr best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

vamp.gr SEO score

100

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

    EL

  • Language Claimed

    EL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vamp.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Vamp.gr 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

vamp.gr

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