Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

spexbay.com

Spexbay Online Store | Sri Lanka's First Online Optical Store

Page Load Speed

10.5 sec in total

First Response

200 ms

Resources Loaded

9.5 sec

Page Rendered

810 ms

spexbay.com screenshot

About Website

Visit spexbay.com now to see the best up-to-date Spexbay content for Sri Lanka and also check out these interesting facts you probably never knew about spexbay.com

Shop spectacles, sunglasses and reading glasses for affordable prices. Spend your money on things that really matter. Now free shipping island-wide in Sri Lanka.

Visit spexbay.com

Key Findings

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

spexbay.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value5,010 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.456

20/100

15%

TTI (Time to Interactive)

Value38.7 s

0/100

10%

Network Requests Diagram

spexbay.com

200 ms

www.spexbay.com

1812 ms

b0713b2546e23e1f5a16e37dcac09ead.css

393 ms

0545e16d40464834454ef3d30fc37185.css

296 ms

2506dfef6c080f50dcda05effb834968.js

486 ms

Our browser made a total of 243 requests to load all elements on the main page. We found that 83% of them (202 requests) were addressed to the original Spexbay.com, 5% (13 requests) were made to Embed.tawk.to and 2% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Spexbay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (46%)

Content Size

2.7 MB

After Optimization

1.4 MB

In fact, the total size of Spexbay.com main page is 2.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. Only a small number of websites need less resources to load. HTML takes 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 954.2 kB
  • After compression 61.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. This page needs HTML code to be minified as it can gain 313.4 kB, which is 25% 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 1.2 MB or 95% of the original size.

Image Optimization

-2%

Potential reduce by 20.1 kB

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

JavaScript Optimization

-12%

Potential reduce by 23.6 kB

  • Original 194.9 kB
  • After minification 194.9 kB
  • After compression 171.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 23.6 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 143 (62%)

Requests Now

231

After Optimization

88

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

Accessibility Review

spexbay.com accessibility score

83

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

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

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

spexbay.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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

spexbay.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Spexbay.com 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 Spexbay.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

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