Tools & Wizards About Us
xccess.in screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

xccess.in

Xccess Mobiles - Android Smartphones | Latest Mobile Phones | 3G Tablets India | Buy Latest Smartphones

Page Load Speed

5.8 sec in total

First Response

1 sec

Resources Loaded

4.4 sec

Page Rendered

352 ms

xccess.in screenshot

About Website

Visit xccess.in now to see the best up-to-date Xccess content for India and also check out these interesting facts you probably never knew about xccess.in

Xccess mobiles presents the best in class range of Android Smartphones, Tablets, Feature phones & IT accessories. View, experience, compare and buy from our latest products.

Visit xccess.in

Key Findings

We analyzed Xccess.in page load time and found that the first response time was 1 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

xccess.in performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.674

8/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

xccess.in

1011 ms

jquery-ui.css

6 ms

jquery-1.10.2.js

9 ms

jquery-ui.js

22 ms

owl.carousel.min.css

236 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 88% of them (50 requests) were addressed to the original Xccess.in, 7% (4 requests) were made to Code.jquery.com and 4% (2 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Xccess.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (39%)

Content Size

3.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xccess.in main page is 3.5 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. 70% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 84.0 kB

  • Original 95.0 kB
  • After minification 53.8 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 41.2 kB, which is 43% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 84.0 kB or 88% of the original size.

Image Optimization

-41%

Potential reduce by 1.3 MB

  • Original 3.2 MB
  • After minification 1.9 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. Obviously, Xccess needs image optimization as it can save up to 1.3 MB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 602 B

  • Original 158.1 kB
  • After minification 158.1 kB
  • After compression 157.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

-4%

Potential reduce by 2.9 kB

  • Original 67.3 kB
  • After minification 67.3 kB
  • After compression 64.4 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. Xccess.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (42%)

Requests Now

48

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xccess.in

xccess.in

1011 ms

jquery-ui.css

jquery-ui.css

6 ms

jquery-1.10.2.js

jquery-1.10.2.js

9 ms

jquery-ui.js

jquery-ui.js

22 ms

owl.carousel.min.css

owl.carousel.min.css

236 ms

owl.theme.default.min.css

owl.theme.default.min.css

472 ms

magnific-popup.css

magnific-popup.css

476 ms

lavaNew.css

lavaNew.css

490 ms

product.css

product.css

499 ms

testimonials.css

testimonials.css

503 ms

carousels.js

carousels.js

515 ms

bootstrap.css

bootstrap.css

712 ms

bootstrap-responsive.css

bootstrap-responsive.css

719 ms

jquery-ui.css

jquery-ui.css

735 ms

nav-style.css

nav-style.css

749 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

757 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1033 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

946 ms

jquery-ui.min.js

jquery-ui.min.js

57 ms

countdown.js

countdown.js

958 ms

main.js

main.js

979 ms

owl.carousel.min.js

owl.carousel.min.js

1001 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1009 ms

myriad-set-pro_text.ttf

myriad-set-pro_text.ttf

925 ms

gif-load.gif

gif-load.gif

241 ms

0.jpg

0.jpg

54 ms

0.jpg

0.jpg

49 ms

search.png

search.png

255 ms

XCCESS%20LOGO.png

XCCESS%20LOGO.png

1531 ms

sprite.png

sprite.png

496 ms

Wave.jpg

Wave.jpg

968 ms

Pulse.jpg

Pulse.jpg

926 ms

A1.jpg

A1.jpg

1252 ms

208.jpg

208.jpg

1491 ms

X493%20Selfie%20New%20Model%20Box%20Design.jpg

X493%20Selfie%20New%20Model%20Box%20Design.jpg

1359 ms

X493.jpg

X493.jpg

1401 ms

IMG_20200629_150724.jpg

IMG_20200629_150724.jpg

1454 ms

33.jpg

33.jpg

1504 ms

32.jpg

32.jpg

1592 ms

X205%2072%20DPI.jpg

X205%2072%20DPI.jpg

1641 ms

X280%2072%20DPI.jpg

X280%2072%20DPI.jpg

1701 ms

blue.jpg

blue.jpg

1992 ms

X492%20Image.jpg

X492%20Image.jpg

1757 ms

X493_BOR_Main.jpg

X493_BOR_Main.jpg

1791 ms

horizontal-separator-line.png

horizontal-separator-line.png

1826 ms

3g_product_name_underline.jpg

3g_product_name_underline.jpg

1890 ms

youtube.png

youtube.png

1945 ms

prev.png

prev.png

2010 ms

next.png

next.png

2049 ms

trigger-btn.png

trigger-btn.png

2059 ms

top-arrow.jpg

top-arrow.jpg

2128 ms

devider.png

devider.png

2190 ms

27674A_0_0.woff

27674A_0_0.woff

2195 ms

27674A_1_0.woff

27674A_1_0.woff

2216 ms

HelveticaNeu.woff

HelveticaNeu.woff

2262 ms

2A6AC2_0_0.woff

2A6AC2_0_0.woff

2247 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

38 ms

Accessibility Review

xccess.in accessibility score

46

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

xccess.in 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xccess.in SEO score

79

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xccess.in can be misinterpreted by Google and other search engines. Our service has detected that English 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 Xccess.in 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

xccess.in

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