Tools & Wizards About Us
urbanaxis.in screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

urbanaxis.in

Urban Axis – Affordable Flats in Lucknow | Best Residential Flats in Lucknow

Page Load Speed

14 sec in total

First Response

2.4 sec

Resources Loaded

10.8 sec

Page Rendered

791 ms

urbanaxis.in screenshot

About Website

Visit urbanaxis.in now to see the best up-to-date Urban Axis content and also check out these interesting facts you probably never knew about urbanaxis.in

Visit urbanaxis.in

Key Findings

We analyzed Urbanaxis.in page load time and found that the first response time was 2.4 sec and then it took 11.6 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

urbanaxis.in performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.3 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value5,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value38.4 s

0/100

10%

Network Requests Diagram

www.urbanaxis.in

2433 ms

opal-boostrap.css

974 ms

custom-frontend-lite.min.css

741 ms

style.css

762 ms

style.css

801 ms

Our browser made a total of 143 requests to load all elements on the main page. We found that 85% of them (121 requests) were addressed to the original Urbanaxis.in, 10% (14 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Urbanaxis.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 529.5 kB (13%)

Content Size

4.2 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Urbanaxis.in main page is 4.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. 75% 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 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 363.9 kB

  • Original 417.8 kB
  • After minification 376.5 kB
  • After compression 53.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 363.9 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 43.8 kB

  • Original 2.8 MB
  • After minification 2.7 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. Urban Axis images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 107.4 kB

  • Original 605.7 kB
  • After minification 605.7 kB
  • After compression 498.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 107.4 kB or 18% of the original size.

CSS Optimization

-4%

Potential reduce by 14.4 kB

  • Original 380.6 kB
  • After minification 380.6 kB
  • After compression 366.2 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. Urbanaxis.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 108 (91%)

Requests Now

119

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.urbanaxis.in

www.urbanaxis.in

2433 ms

opal-boostrap.css

opal-boostrap.css

974 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

741 ms

style.css

style.css

762 ms

style.css

style.css

801 ms

tooltipster.bundle.min.css

tooltipster.bundle.min.css

732 ms

post-122.css

post-122.css

741 ms

magnific-popup.css

magnific-popup.css

740 ms

post-161.css

post-161.css

770 ms

main.css

main.css

975 ms

frontend.css

frontend.css

981 ms

bdt-uikit.css

bdt-uikit.css

992 ms

prime-slider-site.css

prime-slider-site.css

990 ms

premium-addons.min.css

premium-addons.min.css

1041 ms

extendify-utilities.css

extendify-utilities.css

1061 ms

font-awesome.min.css

font-awesome.min.css

1222 ms

sticky-social-icons-public.css

sticky-social-icons-public.css

1229 ms

font-awesome.min.css

font-awesome.min.css

1238 ms

header-footer-elementor.css

header-footer-elementor.css

1241 ms

general.min.css

general.min.css

1296 ms

eael-76.css

eael-76.css

1325 ms

elementor-icons.min.css

elementor-icons.min.css

1467 ms

swiper.min.css

swiper.min.css

1475 ms

post-7.css

post-7.css

1487 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

1487 ms

all.min.css

all.min.css

1554 ms

v4-shims.min.css

v4-shims.min.css

1584 ms

global.css

global.css

1714 ms

post-76.css

post-76.css

1725 ms

custom.css

custom.css

1737 ms

ekiticons.css

ekiticons.css

1739 ms

elegant.css

elegant.css

1812 ms

ionicons.min.css

ionicons.min.css

1845 ms

materialdesignicons.min.css

materialdesignicons.min.css

2207 ms

opal-icons.css

opal-icons.css

1973 ms

carousel.css

carousel.css

1986 ms

css

css

36 ms

css

css

54 ms

js

js

67 ms

js

js

112 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

23 ms

widget-styles.css

widget-styles.css

1999 ms

scc-c2.min.js

scc-c2.min.js

4 ms

responsive.css

responsive.css

1580 ms

fontawesome.min.css

fontawesome.min.css

1598 ms

brands.min.css

brands.min.css

1498 ms

solid.min.css

solid.min.css

1511 ms

widget-carousel.min.css

widget-carousel.min.css

1598 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

1634 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

1688 ms

post-2680.css

post-2680.css

1660 ms

post-2764.css

post-2764.css

1518 ms

post-8876.css

post-8876.css

1516 ms

post-8867.css

post-8867.css

1605 ms

animations.min.css

animations.min.css

1643 ms

intl-tel-input.min.css

intl-tel-input.min.css

1652 ms

wpforms-full.css

wpforms-full.css

1656 ms

jquery.min.js

jquery.min.js

1772 ms

jquery-migrate.min.js

jquery-migrate.min.js

1522 ms

modernizr.custom.js

modernizr.custom.js

1612 ms

fuse_script.js

fuse_script.js

1656 ms

v4-shims.min.js

v4-shims.min.js

1655 ms

owl.carousel.js

owl.carousel.js

1643 ms

carousel.js

carousel.js

1563 ms

slick.js

slick.js

1637 ms

progressbar.min.js

progressbar.min.js

1688 ms

TweenMax.min.js

TweenMax.min.js

2284 ms

tooltipster.bundle.min.js

tooltipster.bundle.min.js

2215 ms

jquery-parallax.js

jquery-parallax.js

2186 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

2056 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

2043 ms

mlpushmenu.js

mlpushmenu.js

2033 ms

classie.js

classie.js

2242 ms

app.js

app.js

2174 ms

dynamic-conditions-public.js

dynamic-conditions-public.js

2141 ms

general.min.js

general.min.js

2011 ms

eael-76.js

eael-76.js

2000 ms

frontend-script.js

frontend-script.js

1918 ms

widget-scripts.js

widget-scripts.js

2085 ms

new-tab.js

new-tab.js

1973 ms

theme.js

theme.js

1960 ms

underscore.min.js

underscore.min.js

1939 ms

wp-util.min.js

wp-util.min.js

1896 ms

sticky-layout.js

sticky-layout.js

1842 ms

navigation.js

navigation.js

2058 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

1969 ms

jquery-numerator.min.js

jquery-numerator.min.js

1966 ms

universal-tilt.min.js

universal-tilt.min.js

1945 ms

premium-addons.min.js

premium-addons.min.js

1960 ms

imagesloaded.min.js

imagesloaded.min.js

1864 ms

bdt-uikit.min.js

bdt-uikit.min.js

2043 ms

webpack.runtime.min.js

webpack.runtime.min.js

1989 ms

frontend-modules.min.js

frontend-modules.min.js

1976 ms

waypoints.min.js

waypoints.min.js

1944 ms

core.min.js

core.min.js

1864 ms

frontend.min.js

frontend.min.js

1822 ms

prime-slider-site.min.js

prime-slider-site.min.js

1975 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1960 ms

hooks.min.js

hooks.min.js

1906 ms

i18n.min.js

i18n.min.js

1894 ms

frontend.min.js

frontend.min.js

1798 ms

FBVwdDflz-iPfoPuIC2iKg0F_U5FIA.woff

FBVwdDflz-iPfoPuIC2iKg0F_U5FIA.woff

597 ms

FBVzdDflz-iPfoPuIC2iIqgn7g.woff

FBVzdDflz-iPfoPuIC2iIqgn7g.woff

598 ms

FBVwdDflz-iPfoPuIC2iKh0C_U5FIA.woff

FBVwdDflz-iPfoPuIC2iKh0C_U5FIA.woff

692 ms

QdVMSTAyLFyeg_IDWvOJmVES_HToIW81Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HToIW81Rbs.woff

692 ms

QdVMSTAyLFyeg_IDWvOJmVES_HSMIG81Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HSMIG81Rbs.woff

812 ms

QdVMSTAyLFyeg_IDWvOJmVES_HSQI281Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HSQI281Rbs.woff

812 ms

QdVMSTAyLFyeg_IDWvOJmVES_HS0Im81Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HS0Im81Rbs.woff

810 ms

QdVMSTAyLFyeg_IDWvOJmVES_HTEJm81Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HTEJm81Rbs.woff

811 ms

QdVPSTAyLFyeg_IDWvOJmVES_Hw3BXw.woff

QdVPSTAyLFyeg_IDWvOJmVES_Hw3BXw.woff

752 ms

QdVMSTAyLFyeg_IDWvOJmVES_HScJ281Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HScJ281Rbs.woff

750 ms

QdVMSTAyLFyeg_IDWvOJmVES_HT4JG81Rbs.woff

QdVMSTAyLFyeg_IDWvOJmVES_HT4JG81Rbs.woff

811 ms

QdVNSTAyLFyeg_IDWvOJmVES_HRUNXgSZg.woff

QdVNSTAyLFyeg_IDWvOJmVES_HRUNXgSZg.woff

810 ms

elements-handlers.min.js

elements-handlers.min.js

1801 ms

background-blog.jpg

background-blog.jpg

867 ms

animate-circle.min.js

animate-circle.min.js

1401 ms

elementor.js

elementor.js

1404 ms

jquery.sticky.min.js

jquery.sticky.min.js

1414 ms

frontend.js

frontend.js

1412 ms

jquery.intl-tel-input.min.js

jquery.intl-tel-input.min.js

1459 ms

jquery.validate.min.js

jquery.validate.min.js

1469 ms

-nFnOHM81r4j6k0gjAW3mujVU2B2G_Bx1A.woff

-nFnOHM81r4j6k0gjAW3mujVU2B2G_Bx1A.woff

155 ms

-nFnOHM81r4j6k0gjAW3mujVU2B2G_5x1A.woff

-nFnOHM81r4j6k0gjAW3mujVU2B2G_5x1A.woff

155 ms

jquery.inputmask.bundle.min.js

jquery.inputmask.bundle.min.js

1436 ms

wpforms.js

wpforms.js

1443 ms

eicons.woff

eicons.woff

1933 ms

opal-icon.woff

opal-icon.woff

1448 ms

ElegantIcons.woff

ElegantIcons.woff

1752 ms

fa-brands-400.woff

fa-brands-400.woff

1799 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

2468 ms

fa-solid-900.woff

fa-solid-900.woff

1982 ms

fa-regular-400.woff

fa-regular-400.woff

1505 ms

elementskit.woff

elementskit.woff

2513 ms

rev_sliderhome_3.jpg

rev_sliderhome_3.jpg

3068 ms

UA-New-Logo.png

UA-New-Logo.png

1840 ms

slider-1-2.jpg

slider-1-2.jpg

2259 ms

slider-2-2.jpg

slider-2-2.jpg

2699 ms

slider-3-2.jpg

slider-3-2.jpg

2607 ms

slider-4-3.jpg

slider-4-3.jpg

2699 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1366 ms

68 ms

intl-tel-input-flags.png

intl-tel-input-flags.png

1285 ms

jquery.intl-tel-input-utils.js

jquery.intl-tel-input-utils.js

271 ms

Accessibility Review

urbanaxis.in accessibility score

83

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 do not have all required [aria-*] attributes

High

[aria-*] attributes do not have valid values

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

urbanaxis.in best practices score

67

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

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

urbanaxis.in SEO score

84

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

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

    EN

  • Encoding

    UTF-8

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

urbanaxis.in

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